Browse thread
Faking concurrency using Unix forks and pipes
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Pablo Polvorin <pablo.polvorin@g...> |
| Subject: | Re: [Caml-list] Faking concurrency using Unix forks and pipes |
> 1. Shared memory and locks should be much faster > for synchronization than marshalling between processes. as long as i don't have to use ugly locks in my code, that will be ok. But I think that the Erlang approach is simpler and more elegant than the use of locks - critical regions. Also, as already mentioned, it offers an easy transition from multicore to distributed computing, where shared memory isn't available. 2007/5/30, Jon Harrop <jon@ffconsultancy.com>: > On Wednesday 30 May 2007 09:13:00 Erik de Castro Lopo wrote: > > How much does a concurrent GC actually buy in comparison to > > multiple processes each with their own GC and a robust way > > of passing data between processes? > > > 2. Forking results in multiple GCs redundantly traversing the same heap and, > worst case, it may end up copying the entire heap in the child process in > order to deallocate it. > > -- > Dr Jon D Harrop, Flying Frog Consultancy Ltd. > OCaml for Scientists > http://www.ffconsultancy.com/products/ocaml_for_scientists/?e > > _______________________________________________ > Caml-list mailing list. Subscription management: > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list > Archives: http://caml.inria.fr > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > -- Pablo Polvorin