We are planning to deploy a memcached cluster of 40 odd machines and were wondering about mgets and the size of the cluster.
We could either: - have all the machines in one cluster, which would mean that an mget on a set of keys could potentially span the entire cluster - partition our cluster into smaller sizes and assign cache lines to certain cluster, thereby reducing the mget fan-out for that cache line Does anyone have any recommendation/benchmarks regarding such a network latency/available bandwidth trade-off? At our current workload, the hosts are not CPU bound. We are using the spymemcached client.
