ns_server needs to deal efficiently with large number of smart client connections that pull streaming vbucket map updates

We've identified that with larger nodes and with lots of client connections we're sometimes eating quite a lot of ram per smart client connection. Current known workaround is to have smart clients randomize node from which vbucket map updates are streamed. But there's likely a lot we can do on server side to dramatically lower memory consumption of such streaming connections.