Concurrent beam?

[Ulf Wiger]

On 7 Mar 2003, Luke Gorrie wrote:

>Ulf Wiger <etxuwig@REDACTED> writes:
>
>> 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.)
>
>Can you elaborate?
>
>My picture of an I/O-bound system is that you've run out of
>I/O resources, and have CPU to spare - so the application
>processing shouldn't affect your performance?
>
>Perhaps there are different flavours of "I/O bound" - are
>you I/O or CPU bound when your select()-loop or kernel is
>overloading the CPU while performing I/O?

You could for example offload the processor running erlang
code by putting protocol stacks (e.g. TCP/IP, SCTP, SAAL,
MTP3, etc) on a different CPU -- unless of course those
protocols are implemented in Erlang... ;)

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