Does data locality matter in HCI Architecture?
Data locality is not just about storing new data in local node. It's also about keeping relevant useful data local when needed for low latency access.
There have been debates whether data locality makes difference in HCI architecture. Some architectures argue that these days with low latency and high bandwidth networks, data locality hardly makes any difference and may end up adding additional bottleneck as hosting nodes are changed. The elegance of architecture comes when it implements data locality entirely considering various workflows such as vSphere HA events and vMotion.
With X-Ray one can see how these workflows are handled by different HCI architectures without much effort from users. These workflows are available as built-in tests for users to kick start as ready to use test.
(i) Database Colocation
What happens when DSS type high-bandwidth workload is deployed in the cluster but in different node? Does that affect existing OLTP workload? Here is the sample X-ray result run on NX-3060-G4. This chart explains all. There is slight increase in latency for OLTP, but both the workloads are handled seamlessly.
(ii) vMotion
This test migrates VM from 1st node to 2nd in 20 minutes and followed by another migration from 2nd node to 3rd node. Both the moves are seamless by maintaining IOPS and slight fluctuations in latency but well under 2ms. Increased network bandwidth shows that AOS architecture gets into action to move data horizontally to the hosting node. The entire process is transparent and data locality is taken care by the architecture as needed.
(iii) VM High Availability
What happens during vSphere HA event? This test brings down a node for vSphere HA to kick in and restart VM on other node. This chart is evident AOS gets into action as soon as VM is powered on other node much before vCenter claims the task complete. AOS migrates data horizontally from other nodes to hosting node utilizing idle network first and then prioritizes VM workload as it finds workload started.
Data locality is not just about storing new data in local node. It's also about keeping relevant useful data local when needed for low latency access.
There have been debates whether data locality makes difference in HCI architecture. Some architectures argue that these days with low latency and high bandwidth networks, data locality hardly makes any difference and may end up adding additional bottleneck as hosting nodes are changed. The elegance of architecture comes when it implements data locality entirely considering various workflows such as vSphere HA events and vMotion.
With X-Ray one can see how these workflows are handled by different HCI architectures without much effort from users. These workflows are available as built-in tests for users to kick start as ready to use test.
(i) Database Colocation
What happens when DSS type high-bandwidth workload is deployed in the cluster but in different node? Does that affect existing OLTP workload? Here is the sample X-ray result run on NX-3060-G4. This chart explains all. There is slight increase in latency for OLTP, but both the workloads are handled seamlessly.
(ii) vMotion
This test migrates VM from 1st node to 2nd in 20 minutes and followed by another migration from 2nd node to 3rd node. Both the moves are seamless by maintaining IOPS and slight fluctuations in latency but well under 2ms. Increased network bandwidth shows that AOS architecture gets into action to move data horizontally to the hosting node. The entire process is transparent and data locality is taken care by the architecture as needed.
(iii) VM High Availability
What happens during vSphere HA event? This test brings down a node for vSphere HA to kick in and restart VM on other node. This chart is evident AOS gets into action as soon as VM is powered on other node much before vCenter claims the task complete. AOS migrates data horizontally from other nodes to hosting node utilizing idle network first and then prioritizes VM workload as it finds workload started.
No comments:
Post a Comment