I'll take a blind stab at this and say that Erlang might actually do
more poorly, unless the chip's interchip message passing is taken
advantage of by Erlang.  If there's a separate piece of hardware
taking on the role of being the messenger, having to waste computer
cycles to send a message isn't terribly efficient.


On Sat, Apr 27, 2013 at 11:17 PM, Cedric Greevey <cgree...@gmail.com> wrote:

> On Sat, Apr 27, 2013 at 11:13 PM, Yves S. Garret <
> yoursurrogate...@gmail.com> wrote:
>
>> How would this compare to Erlang?
>>
>>
>> On Sat, Apr 27, 2013 at 10:51 PM, Cedric Greevey <cgree...@gmail.com>wrote:
>>
>>> https://en.wikipedia.org/wiki/Intel_MIC
>>>
>>> 50+ cores?! Clojure will leave every other language in the dust on
>>> something like that, thanks to its inherently scaleable concurrency
>>> constructs. Try writing a 50-threaded Java application without getting
>>> deadlocks all over the place, or cheating and using very coarse-grained
>>> locks (have fun with the task manager showing 2% CPU utilization when your
>>> app is running full-bore!).
>>>
>>> If big, 32-bit addressing spaces were what made automatic memory
>>> management really begin to come into its own (and with it, Java), then it's
>>> doubtless 50-core machines that will make automatic concurrency management
>>> really begin to come into its own.
>>>
>>
> Erlang might also do well on such a machine. The actor model likely
> involves more communication among the cores to get full utilization, but
> then, the page describes some sort of message-passing system among the
> cores on MIC, so ...
>
>  --
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to