<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
Thats the idea. If one is to scale a system across a network, then
you'll see performance increase, not to mention code complexity will
roughly increase linearly (in my experience) with erlang and
exponentially with traditionally imperative languages like C++ or Java.<br>
<br>
Zac<br>
<br>
Hugh Perkins wrote:
<blockquote
cite="mid:837db430709061557m27498d46hb16721ae8689a49e@mail.gmail.com"
type="cite">
<pre wrap="">On 9/7/07, Zac Brown <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:zac@zacbrown.org"><zac@zacbrown.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> I think I'm less irritated with the inaccurate results than I am with the
fact that "method invocation" has suddenly become equivalent to
multi-threading/parallel execution.
Odd how simple it is to bend our tests to our whim eh?
</pre>
</blockquote>
<pre wrap=""><!---->
Presumably the issue is that the tests were on a single-core system,
where true threading doesnt give any speed advantage?
If one tested on a 64-core system, presumably the Erlang solution
would be obviously better, and the other solutions would need to use
threading too to get somewhere close?
_______________________________________________
erlang-questions mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.erlang.org/mailman/listinfo/erlang-questions">http://www.erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>