5 ms·
This is the way forward. A wasm-instance-per-actor architecture enables: - Actor prioritization - Actor pausing - Killing actors at arbitrary points - Actor
by nahuel0x 6y ago
This is the way forward. A wasm-instance-per-actor architecture enables:
- Actor prioritization
- Actor pausing
- Killing actors at arbitrary points
- Actor serialization / migration
- per Actor GC (internal to them)
- Multiple languages
- Inter-actor/host protected shared memory in addition to message passing
Has the potential to be better than Erlang and much, much better than Go.
- dnautics 6y ago> Has the potential to be better than Erlang what's the overhead of a wasm instance?
- ReactiveJelly 6y agoAuthor claims 4 KB for a stack page here: https://news.ycombinator.com/item?id=25163677 https://news.ycombinator.com/item?id=25163677
- cutemonster 6y agoWhat about Erlang? 4k sound like not that much to me? Imagine a server with 1M concurrent connections, could it need just 4G? (Plus lots of overheard. And without heap)