2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Erlang |
From: | Kay-Uwe Kasemir <[email protected]> |
To: | Core talk list <[email protected]> |
Date: | Fri, 24 Feb 2006 16:35:11 -0500 |
On Feb 24, 2006, at 16:13 , Benjamin Franksen wrote:
However, its built-in concurrency and distribution support is extremelyefficient and scalable. This can easily tip the balance for code that is heavily multi-threaded and/or distributed. See for instance http://www.sics.se/~joe/apachevsyaws.html. BTW, Erlang is reported tohave been benchmarked with 20 million (!) processes on a single machine(the latest UltraSPARC with lots of memory, IIRC). Of course, Erlang's runtime system is written in (fine-tuned, hand-optimized) C...
So what do we do with it? Replace records with Erlang processes and channel access with Erlang's message passing? Try to reach the same robustness by also passing everything as a copy with garbage collection, i.e. re-implement Erlang's GC and message passing? Ignore it and keep passing pointers within the same process? -Kay