Concurrent beam?

[Ulf Wiger]

On 7 Mar 2003, Luke Gorrie wrote:

>So what I wondered was, in Erlang style, might it be easier
>to write a concurrent emulator rather than a parallel one,
>with one thread per logically concurrent activity?
>
>For example, one thread executes erlang processes, one
>garbage collects, one does I/O, etc?

I believe it could be a big win for some projects (don't ask
me for examples) just to be able to locate members of the
thread pool onto a different (or several different) CPU.

Separating application- and I/O processing is one of the
most efficient ways of increasing performance in I/O-bound
systems (and I believe many Erlang-based products are
I/O-bound.)

/Uffe

-- 
Ulf Wiger, Senior Specialist,
   / / /   Architecture & Design of Carrier-Class Software
  / / /    Strategic Product & System Management
 / / /     Ericsson AB, Connectivity and Control Nodes