News for hackers. Stuff that matters.
Re:Why Erlang? by hungryblank on Monday April 23, 2012 @05:38AM (#3878022)
BEAM has this very interesting concept of scheduling, working from a very high level point of view as follow

1) there are a number of processes wanting to be executed

2) schedulers (generally one per core but is a configuration option) schedule on process and run it for a fair amount of operations. This makes systems with heavy parallelism run very smoothly since single processes won't hog cores but will only get a fair amount of scheduling.

On top of that the fact that the BEAM is directly aware of processes (actors) makes the system very transparent (you can look in depth into a single process and examine it's heap size, scheduling consumption google for erlang process_info to get an idea)

Very interesting with this regard are the slides about the erlang VM by Robert Virding http://goo.gl/PHfeh and from erlang "half word" VM talk by Patrik Nyblom http://goo.gl/2LD9S

There are no comments on this comment yet.