Andrew Lentvorski wrote:
First, nothing may be shared. All communication is by messages that
are copied. This has interesting performance tradeoffs.
Not really. There is no requirement that an actual copy happen.
There is a comparison between Gambit/Termite and Erlang where you
see that Erlang benefits as long as the messages are small and starts
to die when the messages get big--Gambit/Termite is the reverse.
Erlang's runtime does need to be optimized better for larger messages.
Second, it puts watchdogs over things and if they lock, it kills and
restarts them. That solves the *symptom*, but not the problem.
Again, the halting problem... sometimes all you can solve is the symptom.
Third, all messages are received asynchronously, so you have to
account for that outright in your coding style.
Isn't the assumption that messages can be passed instantly between two
nodes on of those "Myths of distributed computing"?
--Chris
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
