Re:MemSQL ships 2.0, scales across hundreds of nodes, thousa...
by simcop2387 on Tuesday April 23, 2013 @02:57PM
(#5597206)
The problem is that you can end up with larger latency over the network because it still takes a fixed amount of time for nodes to communicate. Even with a 1TB/s link between nodes you can still have a good 30ms between them all adding even more latency. That can be mitigated somewhat by a good protocol that can manage that latency properly (e.g. not blocking while waiting on ACKs and such), it can still end up with far more latency than a few large disks would be (even better now with SSDs). That said I do imagine that some datasets will benefit from this kind of topology (I can imagine that geospatial stuff will do well with that, since you can locate physically close things on a single machine and reduce the amount of talking needed).
[ Parent
| on HN ]
Re:MemSQL ships 2.0, scales across hundreds of nodes, thousa...
by TylerE on Tuesday April 23, 2013 @04:01PM
(#5597584)
30ms? In anything resembling a modern datacenter? 0.3-0.5ms is more typical these days.
Re:MemSQL ships 2.0, scales across hundreds of nodes, thousa...
by brianatdts on Tuesday April 23, 2013 @03:25PM
(#5597372)
He was joking.