No batching or sensible delivery scheme for mass-updates to new servers

[ashleydavies]

When a new server joins the pool, all of the existing information in the pool needs to be synced to it. In theory, this information could be batched or transmitted intelligently in a way that minimises the number of messages sent. In practice, data-pooler currently just sends messages at a rate of 2Hz per server. You may find this overwhelms your rate limits if you use multiple pools or use MessagingService for other uses.