this post was submitted on 22 Nov 2023
1 points (100.0% liked)
Homelab
371 readers
9 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
GID VMNAME NVDISK CMDS/s READS/s WRITES/s MBREAD/s MBWRTN/s LAT/rd LAT/wr
12953 dns - 1 0.00 0.00 0.00 0.00 0.00 0.000 0.000
16904 fw - 2 5.84 0.00 5.84 0.00 0.02 0.000 18.408
20481 vcsa - 13 16.58 0.00 16.58 0.00 0.08 0.000 37.582
130847 - 2 0.00 0.00 0.00 0.00 0.00 0.000 0.000
626694 deb - 2 12.06 0.00 12.06 0.00 0.46 0.000 6.586
as you can see the is no much IOPS per VM, like vcsa VM latency I captured is floating between 20 and 100ms, while deb has similar IOPS but lower latency
I think what you want to do is go into your db vm and run a DD or fio or bonnie++ that is at least 2 x the VM RAM, and see what the steady-state disk performance is.
I don’t have db VM, I think you are referring to deb which is short for Debian.