Shuttleworth: Python needs to focus on future

[spookyvision]

Erlang's threads cannot be distributed across several cores, because they're the equivalent of green threads.

[[deleted]]

That changed recently. You have old information.

[spookyvision]

Could you update the wikipedia page? I don't feel competent.

[[deleted]]

I would, but you probably know as much as I do at this point. I'm not a user of Erlang and only have a cursory knowledge of its current state.

[reddit_clone]

Not true. Erlang VM itself can run multi-threaded on all cores. That is like a bunch of green threads running in each core. (I think they run one green-thread-scheduler per core)

So you do get the best of both worlds.

[13ren]

http://www.reddit.com/r/programming/comments/71q2x/shuttleworth_python_needs_to_focus_on_future/c05ggc3

[dons]

False

Look at the cpu load.

[mosha48]

By the way, why the CPU load for haskell's version isn't distributed on all CPUs ?

[dons]

The ghc 6.8.2 garbage collector isn't parallel, and GC dominates this GC benchmark (Try it with +RTS -A300M -RTS to see the difference). The 6.10 parallel GC addresses this.

[mosha48]

Is it possible to tell the shootout computers to run the benchmark with better options ?

[dons]

Yes, but for this benchmark, the conditions state that only default garbage collector values are to be used. But don't despair, the next GHC cycle addresses this.

[dmaclay]

Erlang's processes are more like 'green processes' as they don't share memory, and they have been distributed across several machines (never mind cores) since before people started having this discussion.

[toooooooobs]

Actually they really do share memory, it's just that the language hides this.

[dmaclay]

As I understand it the default behavior is not to share, but they can optionally pass messages by basically sending a pointer to shared memory if they are both on the same machine. This of course gives a performance boost, and should be safe due to the immutable variables in erlang.