safelyRemove
n00b
- Joined
- Dec 13, 2012
- Messages
- 46
I am using FreeBSD 9.1 with a 3ware 9650se and ZFS (raidz2). Latest firmware on the 9650, and latest drivers on FreeBSD.
It has three types of StorSave performance profiles, Protect, Balance, and Performance.
First, when I have drives on the built-in AHCI ports, the drive lights will illuminate in bursts during a write, as expected, and then go out.
On the 3ware, in Performance mode, the lights all come on at the same time, as expected, but roughly 7 seconds after the lights go on with AHCI-ported drives. So, the 3ware is caching. OK.
In Balance mode, the caching doesn't happen, and the lights on both AHCI and 3ware will come on at the same time, BUT, the AHCI drives finish very quickly and go out, while the 3ware drives suddenly begin lighting up one at a time, in proportion to the amount of data written, then they all light up again (serially, for the uber-blocks I assume), and go out. It is much slower, and it is slower than AHCI performance.
There are no in-between settings on the 3ware that I am aware of. I believe when ZFS issues the flush command, the 3ware card begins serializing the writes across *all* ports, rather than letting each drive work in parallel as it should. (The drives are configured as JBOD.) ZFS mirror vdevs have the same behavior.
Can anyone else confirm this, or have ideas to have the 3ware match the AHCI behavior (no 7 second unnecessary caching, but no serializing across ports, either)?
It has three types of StorSave performance profiles, Protect, Balance, and Performance.
First, when I have drives on the built-in AHCI ports, the drive lights will illuminate in bursts during a write, as expected, and then go out.
On the 3ware, in Performance mode, the lights all come on at the same time, as expected, but roughly 7 seconds after the lights go on with AHCI-ported drives. So, the 3ware is caching. OK.
In Balance mode, the caching doesn't happen, and the lights on both AHCI and 3ware will come on at the same time, BUT, the AHCI drives finish very quickly and go out, while the 3ware drives suddenly begin lighting up one at a time, in proportion to the amount of data written, then they all light up again (serially, for the uber-blocks I assume), and go out. It is much slower, and it is slower than AHCI performance.
There are no in-between settings on the 3ware that I am aware of. I believe when ZFS issues the flush command, the 3ware card begins serializing the writes across *all* ports, rather than letting each drive work in parallel as it should. (The drives are configured as JBOD.) ZFS mirror vdevs have the same behavior.
Can anyone else confirm this, or have ideas to have the 3ware match the AHCI behavior (no 7 second unnecessary caching, but no serializing across ports, either)?