Unsolved
This post is more than 5 years old
2 Intern
•
470 Posts
0
2389
May 6th, 2012 00:00
iometer test
i tried to run some test on an unformatted disk and got about 3000io/sec and only 12mb/savg io time was about 19. the disk is on a R5 sata RG 1.5TB and nothing is really on the RG.
why is it so slow?
0 events found
No Events found!


dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 6th, 2012 02:00
need more info, what settings did you use in IOmeter. IO size, read/write ratio, seq / random ..etc
zhouzengchao
6 Operator
•
1.4K Posts
0
May 6th, 2012 03:00
Also the number of threads is needed...FC or iSCSI connection...
tdubb123
2 Intern
•
470 Posts
0
May 6th, 2012 09:00
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 6th, 2012 10:00
did you mean to attach something ?
tdubb123
2 Intern
•
470 Posts
0
May 6th, 2012 11:00
Not sure what happened.
Here is my response
This is fiber connection.
Using 4k 100% write random
2000000 sectors
64 targets per io
tdubb123
2 Intern
•
470 Posts
0
May 6th, 2012 12:00
The results are changing.
Now I am getting 20000io/s
75mb/s
Av ioresp 3ms
Max io resp 476ms
I had to remove the rdm from the vm. Shutdown the vm and readd to restart any iometer tests. Why?
Are these acceptable results?
tdubb123
2 Intern
•
470 Posts
0
May 6th, 2012 13:00
Not sure why. It starts out at 25000iops and then drops down to 1500 iops
tkjoffs
159 Posts
0
May 6th, 2012 20:00
There are a lot of variables here. Can one assume from the fact that you are performing IOMeter tests that the following is true:
Assuming all that is correct, can you look at the performance logs for the array and see any bottlenecks at the LUN. RG, or SP sides? On the host, can you tell us if you are getting any Queuing and what the number is?
A few other questions:
Happy to help if you can provide more data.
Thanks.
RRR
6 Operator
•
5.7K Posts
0
July 3rd, 2012 03:00
First the write cache fills up and you'll get a really good IO rate. After the write cache is full, the IOps drop down to a steady state, which in your case is 1500. In the background the write cache will do flushings to disk and on the front end your test machine is filling up the cache, so this 1500 is the actual speed you're getting from the disks, since they are the weakest link.