GV Govindasamy (Nutanix Senior Solutions and Performance Engineer ) has written a series of three blog posts on data locality, I thought I would summarize and share them here. Be the first to reply with a question below.
Does data locality really matter?
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. Read more.
Can data locality help scale throughput?
X-Ray's throughput-scalability-random-reads and throughput-scalability-sequential-reads tests help answer the following: Can IOPS or throughput rate sustain over time? As number of nodes grow in cluster, can throughput or IOPS scale with it? Read more.
What if Data Locality was not a design choice in Nutanix AOS?
What if data locality was not considered in Nutanix AOS architecture like a few other HCI architectures available in the market? Would AOS suffer the same as other architectures for high throughput workloads such as DSS? Read more.
Be sure to share your thoughts in the comments below. Consider clicking the 'like' if you enjoyed this roundup.
This topic has been closed for comments
Data Locality is easily glossed over with all of the other cool features and since it has just been there since the beginning. But it is so important as a feature that sets NTNX apart from the wanna be copy cats.
Already have an account? Login
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.