I've been browsing the Doug Bagley Shootout pages:
http://www.bagley.org/~doug/shootout/ and Erlang does spectacularly badly in
quite a few areas where it shouldn't really be quite that bad.
I'm thinking of the Echo Client/Server which sends messages via an INET
socket from one process to another. All the others use two Native processes
but the Erlang one uses lightweight threads and still manages to be nearly
three times slower than all the others.
Also in Count Lines/Words/Chars Erlang uses 56Mbytes of RAM where the
nearest other is Java at 7M and the majority come in with less than 2. Even
at 8 octets per char it shouldn't use 25 times more memory..
Now I know that benchmarks are not representative etc etc but they do
encapsulate quite a few common idioms and there shouldn't be a good reason
for Erlang to do so badly. Maybe the HIPE guys can use (are using?) these in
their investigations into optimal GC schemes etc for R8?
This sort of thing does put people off, and I for one have bought a lot more
RAM than my applications should need just in case...
General moan over..
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.