[erlang-questions] Concurrency Orientated Design question

Jesper Louis Andersen <>
Mon Feb 7 20:13:49 CET 2011


On Mon, Feb 7, 2011 at 19:29, Marcel Meyer <> wrote:

> Scenario 2:
> Spawn an "owner" tree processor, and on all "read-like" operations, spawn a
> new process to deal with that request.
> The good:
> Better scaling
> The bad:
> Spawning a new process with the existing state might be expensive (ito
> memory and time), as these trees could be large (4Mb max, usually < 200kb).
> Updating the tree will become hairy, unless updates are only done by the
> owner, like when you spawn an ets table as private.

Scenario 3:

The tree nodes are stored in ETS. Otherwise it is like scenario 2.

Scenario 4:

Each tree node is a process :)
-- 
J.


More information about the erlang-questions mailing list