This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.
Solved
OS IOPS value Vs Storage IOPS value
Posted on 2012-12-27
How do we differentiate the IOPS value from OS to Storage. For an example I'm writing 8K block of data using dd command in linux
dd if=/dev/zero of=/opt/rg/perf/testing123
245760000000 bytes (246 GB) copied, 334.014 s, 736 MB/s
IOPS value is 30000000/334= 89820
but in Storage I'm only seeing around 2000 IOPS. IF I understand correctly it converts to different block size, and then do the calculation?
dd if=/dev/zero of=/opt/rg/perf/testing123
245760000000 bytes (246 GB) copied, 334.014 s, 736 MB/s
IOPS value is 30000000/334= 89820
but in Storage I'm only seeing around 2000 IOPS. IF I understand correctly it converts to different block size, and then do the calculation?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3-
3
7 Comments
Active today
dd does NOT write data to the HDD in 8KB I/O chunks, or for that matter, the way you are running it, it won't even write only 8KB x 30000000 bytes of data.
Your filesystem, kernel, and device drivers are doing a heck of a lot of things underneath the covers such as dealing with journaling, aggregating I/O, and potentially doing some compression depending on some settings.
It is even queuing I/O, so if you kill the dd, you will note that the HDD still blinks for a while after dd is killed.
If you want to measure how fast data gets to the disk, with reasonable accuracy, you must do a dd but set the of= to the raw physical device (which destroys file system). If you want to insure that the block sizes are correct and when you do a dd to write chunks in 8KB and exactly 8KB of data gets written and nothing else, then you have to write a program that uses the pass-through /dev/sg driver and send out the WRITE(10) and/or WRITE(16) CDBs. The raw SCSI method is the ONLY accurate means of having complete control.
Your filesystem, kernel, and device drivers are doing a heck of a lot of things underneath the covers such as dealing with journaling, aggregating I/O, and potentially doing some compression depending on some settings.
It is even queuing I/O, so if you kill the dd, you will note that the HDD still blinks for a while after dd is killed.
If you want to measure how fast data gets to the disk, with reasonable accuracy, you must do a dd but set the of= to the raw physical device (which destroys file system). If you want to insure that the block sizes are correct and when you do a dd to write chunks in 8KB and exactly 8KB of data gets written and nothing else, then you have to write a program that uses the pass-through /dev/sg driver and send out the WRITE(10) and/or WRITE(16) CDBs. The raw SCSI method is the ONLY accurate means of having complete control.
Same goes for Windows, the device driver will even re-order writes to try to make bigger I/Os to cut down the IOPS requirement especially if it's a clever RAID controller.
Active today
Thank you very much. If I'm writing to raw device, then how do I much up IOPS value with storage? Does it need to be equal or depends on the storage and stripe size?
Active today
There is no such thing as stripe size when sending raw WRITE commands to the HDD. If you send it 2,618 bytes, then that is what it writes. IF you send 32,768 bytes, then that is what it writes.
Now what i think you want to do is send raw SCSI commands to the RAID volume, and that process depends on whether you are doing hardware or software RAID .. so be specific, what is the method you use for RAID?
Now what i think you want to do is send raw SCSI commands to the RAID volume, and that process depends on whether you are doing hardware or software RAID .. so be specific, what is the method you use for RAID?
Active today
No, I mean in storage side, does it convert to different stripe size and write it to disk?
Active today
If you send the raw scsi commands to the RAID volume, then the controller will slice and dice as necessary to get it to the disk. Example, if stripe size is 64KB and you have a 3-disk RAID5, then if you send just one byte to the raid volume, then this will generate approx 256KB worth of I/O.
But if you read 1 byte, then that could generate anywhere from 1 byte to 64KB worth of physical disk I/O.
It is all dependent on understanding the RAID architecture.
But if you read 1 byte, then that could generate anywhere from 1 byte to 64KB worth of physical disk I/O.
It is all dependent on understanding the RAID architecture.
Featured Post
Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Each year, investment in cloud platforms grows more than 20% (https://www.immun.io/hubfs/Immunio_2016/Content/Marketing/Cloud-Security-Report-2016.pdf?submissionGuid=a8d80a00-6fee-4b85-81db-a4e28f681762) as an increasing number of companies begin to…
A look at what happened in the Verizon cloud breach.
Learn how to get help with Linux/Unix bash shell commands.
Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Learn how to find files with the shell using the find and locate commands.
Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Suggested Courses
Course of the Month13 days, 14 hours left to enroll
656 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.