I would be much more interesting in seeing 5000 under heavy load.
Just being able to star that many instances is not that exciting until we know what they can do.
I would be much more interesting in seeing 5000 under heavy load.
Just being able to star that many instances is not that exciting until we know what they can do.
Erlang handles heavy load VERY well, between work stealing schedulers and soft realtime via reduction counting (any program can be interrupted and stopped after any instruction and resumed transparently)
That is good. Then actual propper benchmarks will be remarkable.
However BEAM is not the only factor in this process. the entire hardware platform as well.
This is after all a lot about that nice and huge cpu.
I mean when you have all 5000 started why not let the do some work? Stress test it with a few real life scenarios for 48h and let us see some number.
I will consider it :)