Re: [zfs-discuss] StorageTek 2540 performance radically changed

2009-04-20 Thread Robert Milkowski
Hello Bob, Wednesday, April 15, 2009, 1:01:02 AM, you wrote: BF Today I updated the firmware on my StorageTek 2540 to the latest BF recommended version and am seeing radically difference performance BF when testing with iozone than I did in February of 2008. I am using BF Solaris 10 U5 with

Re: [zfs-discuss] StorageTek 2540 performance radically changed

2009-04-20 Thread Bob Friesenhahn
On Tue, 21 Apr 2009, Robert Milkowski wrote: BF One change is that I had applied a firmware tweak from Joel Miller BF (apparently no longer at Sun) to tell the array to ignore cache sync BF commands (i.e. don't wait for disk). This updated firmware seems BF totally different so it is unlikely

Re: [zfs-discuss] StorageTek 2540 performance radically changed

2009-04-20 Thread Torrey McMahon
On 4/20/2009 7:26 PM, Robert Milkowski wrote: Well, you need to disable cache flushes on zfs side then (or make a firmware change work) and it will make a difference. If you're running recent OpenSolaris/Solaris/SX builds you shouldn't have to disable cache flushing on the array. The

Re: [zfs-discuss] StorageTek 2540 performance radically changed

2009-04-20 Thread Bob Friesenhahn
On Mon, 20 Apr 2009, Torrey McMahon wrote: On 4/20/2009 7:26 PM, Robert Milkowski wrote: Well, you need to disable cache flushes on zfs side then (or make a firmware change work) and it will make a difference. If you're running recent OpenSolaris/Solaris/SX builds you shouldn't have to

[zfs-discuss] StorageTek 2540 performance radically changed

2009-04-14 Thread Bob Friesenhahn
Today I updated the firmware on my StorageTek 2540 to the latest recommended version and am seeing radically difference performance when testing with iozone than I did in February of 2008. I am using Solaris 10 U5 with all the latest patches. This is the performance achieved (on a 32GB file)

Re: [zfs-discuss] StorageTek 2540 performance radically changed

2009-04-14 Thread Bob Friesenhahn
I should have allowed the iozone run to go futher. What is really interesting is that performance is very much tied to file size: KB reclen write rewritereadreread 33554432 64 76688 27870 552106 555438 33554432 128 103120 369527