3 ms·
pony is compiled to native code, and to highly optimized code. beam is just interpreted. even if most of the time the code has to wait, it has to wait much less
by rurban 10y ago
pony is compiled to native code, and to highly optimized code.
beam is just interpreted. even if most of the time the code has to wait, it has to wait much less. that's why pony can beat C++ with OpenMP in comparable tasks.
It's garbage collector is superior, having to do much less work than in beam.
The data workload for each thread is much smaller. objects are tiny, messages are mostly referenced (shared) and not copied.
erlang does more. it already supports distributed actors, so there's a little overhead also.
- PeCaN 10y agoCurious, how is Pony's GC superior to Erlang? Erlang's GC is already pretty quick (since the heaps are very small).
- doublec 10y agoThere's a thread here from a previous discussion: https://news.ycombinator.com/item?id=9483071 https://news.ycombinator.com/item?id=9483071 One nice thing about the Pony GC is it can GC actors that are waiting for messages but will never receive one. In some other languages I've used I end up with processes idling in a receive on channel living forever but never able to exit because nothing is going to put a message in the channel.