The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
kmax wrote:Your original thread inspired me to do some testing with Atto over the past few days.
I had terrible read performance with 512 bytes. That led me to this article:
http://sustainablesharepoint.wordpress. ... ith-iscsi/
As for the results...this is before changing (or adding since it wasn't in the registry) the registry entry: And this is after: Default is a 200ms delay, the entry removes this and fires it off right away. My understanding is the default waits until the frame fills up (jumbo) to send the request and after 200ms sends it anyways.
The odd thing is if I set queue depth lower than 3 in Atto the performance is OK.
Also, the results are against a RAM disk on a single Starwind node.
nbarsotti wrote:ggalley wrote:Hello I work for a large company that is investigating rolling out starwind to replace some of our SAN environment but I cannot recommend starwind 5.6 due to performance issues.
I have also spent several weeks trying to figure out why the performance is all over the place with starwind 5.6. /quote]
After looking at your ATTO benchmarks I am in a very similar situation as yourself and I have also not found a solution. I am running a 14 SSD raid10 array and I very similar numbers to ggalley. I wish I had some advice, but I will be following this thread. To answer anton's questions
1) I have 1 machine no HA
2) I do not use Write-Back cache on my starwind target I use write-through. Cache is 4GB, expire time is 5000ms
4) no jumbo frames since my switch does not support it
6) hard to test 10GB iscsi numbers since the only other host with 10gb NIC is the ESXi host.