Swarm: A true distributed programming language
blog.locut.us
blog.locut.us
The article says that 3.5% of instructions cause a continuation to be sent. That's a huge percentage. A program would spend all its time marshaling and unmarshaling.
One of the things that you want to do to increase efficiency is to promote and exploit locality. You want to cluster the closely related objects on the same node to reduce network traffic and latency. Constant moving of objects or a bad distribution strategy is going to hurt that. I once worked on a distributed database with automatic replication to ransom nodes. Performance was killed by constant network chatter. The design goal was 1000 nodes, in reality it maxed out at 16.