The elevator is set to deadline: Command line used: iozone -t1 -i0 -i1 -i2 -r1m -s24gĪnother reason to be wary of large RAID 5 arrays. I just ran the following iozone command line on an XFS partition contained within a D元80 G5 with P400i, 12GB RAM and 8 x 146GB 10k drives.
Over time, I've ended up with mount parameters very similar to the one in the original link. If you do go with XFS, try a basic config then try some advanced configuration settings. noop or deadline, in this case) that can be tuned, but that's a function of your application's actual needs. You have I/O scheduler and elevator settings (e.g. I don't use LVM, especially with HP controllers that can provide many of the same benefits. noatime) and journal settings you could tweak. XFS will make a difference, but what are you tuning for? Are you tuning to simply achieve specific numbers, or is there an application requirement driving this?Įxt3 isn't the fastest filesystem out there. I prefer to have 75% write cache because the OS (using the XFS filesystem) caches aggressively.
I typically set Smart Array controllers to leverage a higher write cache ratio. This is several questions in one, so I'll try to address a few of them.
0 kommentar(er)
