
Howard Marks28








What do you folks think about data locality? If the same group of servers are doing compute and storage should the data for a VM be on the server where that VM is running? or is that adding complexity?

David Nicholson
It is a trade off. Parallelism can be powerful. Compromise is an ability to create "domains" and "pick your media/connectivity".

Ed Beauvais
Generally speaking, data is sticker, and moving the compute or having it co-resident is an advantage that #serversan has. added benefits are also reduced latency

Howard Marks some of the products do locality and others don't. Which has lower latency and net traffic? We'll have to see.

Jeff Frick
@dfloyer -> Part of David Floyer's Mega Data Center story.

John F. Kim Not to be confused with BMW's Mega City (i3) story
Rodger Burkley
Why would you want that in a virtualized server San fabric? What about VM migrations to other physical hosts?

Chris Wilson
Ideally you'd like it close but the devil will be in the detail. What happens when you want to replace a node(s)....

Chuck Hollis
We go back and forth. For some apps (e.g. Hadoop), the benefit could be worthwhile. For others, not so clear. And then there is the complexity factor.

Jesse St. Laurent
It is almost always easier to move the VM than the data. A few GB of vRAM vs. 100s of GB of data

Barry Ader
then the system needs to be smart enough to handle that in a resilient elegant manner

Jesse St. Laurent
The admin should not need to know or care. The system should simply make this decision.