3 ms·
In that case the fastest way to do it in Rust would be to use an iterator.
by pcwalton 13y ago
In that case the fastest way to do it in Rust would be to use an iterator.
- derefr 13y agoOh, sorry, forgot to include: 1. Only the agent that outputs a signal knows where it should be propagated[1]. (The decision of propagation is part of the each agent's internal state.) and 2. Each agent may be running on a different system than the next, and may propagate the signal using a network call instead of an internal message-pass-and-yield. Chinese Whispers is inherently a test of message passing in a distributed system. An iterator-based design (e.g. a "controller" agent that pulls in the state after each call and sends it to the next agent, forcing a hub-and-spoke series of RPC calls) will • tend to introduce highly-degraded performance, since you've doubled the number of messages being sent; • force a synchronous wait in the controller (it can't do anything until it's talked to everyone, whereas with the asynchronous propagation, all it has to do is "kick it off"); • possibly just not work at all--if, for example, an agent propagates into a private network that only accepts messages from that agent, not from your controller. --- [1] The Chinese Whispers problem includes a set-up phase, where the controller instantiates the agents and wires them to one-another. This is just for the sake of convenience, though; the controller should not be assumed to have knowledge of how the agents are interconnected once it has the ring established.
- pcwalton 13y agoThis particular benchmark is especially poor if that's what it's trying to test then, because this benchmark is completely gated on task/goroutine spawning performance and message passing barely even shows up in the profile in both Rust and Go.
- masklinn 13y agoYes a "fairer" evaluation of "chinese whispers" would first setup the whole thing, then start the test and send a message into the ring.