This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.
vmware I/O tuning question
I'm dong stress testing on VM and when I look at the queue ACTV is going to 32 and once it is 32, I can see QUE is increasing. I understood that max que size is 32. IF I want to get better IO for that , what can I do? Can I add another que? IF so, how can I add?
Asked:
3-
3
1 Solution
Can we increase the Que size for specific VMs, I know that we have enough space on our storage and enough IOPS available.
Increasing the queue size won't do squat for you. The amount of free space has nothing to do with the fact that there are so many I/Os queued up because your disks are so busy.
A HDD can only move X amount of data (or # of transactions) in Y amount of time. You have 32 queued up transactions to do. So you need to lower X (buy more disks or do fewer requests), or get faster devices, which improves Y.
A HDD can only move X amount of data (or # of transactions) in Y amount of time. You have 32 queued up transactions to do. So you need to lower X (buy more disks or do fewer requests), or get faster devices, which improves Y.
Thank you very much. If I understand correctly the queue is getting filled because storage can't handle it?
Exactly. Hence the need to do one of the things I mentioned. You are simply asking too much of what you have.
Equate it to not having enough RAM, and you keep piling up programs to run. Think of this queue depth as being somewhat like swap space for I/O requests. The solution to not enough RAM is to run fewer programs, or buy more RAM.
Equate it to not having enough RAM, and you keep piling up programs to run. Think of this queue depth as being somewhat like swap space for I/O requests. The solution to not enough RAM is to run fewer programs, or buy more RAM.
It's not quite as simple as all that... you could be slowed down in your I/O because the interface specifications (and requisite drivers) may not be optimal...
When I first switched from Xen to KVM (in a RHEL world), I was aghast at the slowness of KVM -- especially given the advertised "efficiency" KVM was supposed to have!
As it turned out, when I switched the storage from IDE to virtio, and then network from RealTek to virtio, my systems actually DID see significant performance gains... (BTW: I also migrated from raw IMG files to qcow2 formatted (pre-allocated) files...
I'm not sure of the equivalents in VMware, but I thought it worth noting that virtual machines can have different virtual interfaces with their virtual host that can have VERY different performance characteristics...
Dan
IT4SOHO
When I first switched from Xen to KVM (in a RHEL world), I was aghast at the slowness of KVM -- especially given the advertised "efficiency" KVM was supposed to have!
As it turned out, when I switched the storage from IDE to virtio, and then network from RealTek to virtio, my systems actually DID see significant performance gains... (BTW: I also migrated from raw IMG files to qcow2 formatted (pre-allocated) files...
I'm not sure of the equivalents in VMware, but I thought it worth noting that virtual machines can have different virtual interfaces with their virtual host that can have VERY different performance characteristics...
Dan
IT4SOHO
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Bottom line, this isn't rocket science. There are 32 requests for I/O so you need to change things to keep the todo list shorter.