Posted by: Anonymous Coward
on February 09, 2005 11:54 PM
Actually mounting HFS under solaris without logging *decreases* IO throughput. Every document on DB scalability regarding Solaris recommends to mount FS *with* logging.
Another thing You have to check - if MySQL does caching (most databases do - but don't know abut MySQL) is if Your FS block size matches DB cache block size. If Not You can init Your HFS filesystem with block size equal (or multiply) to DB block size (in case of oracle it speed up heavy IO operations 2-3 times).
And You can use forcedirectio mount option for data/index files (but only for these files!) - so You flush Your data without any OS caching and baypassing kernel. (In case of oracle is speed up IO operations by factor 4(!)).
Finally please check Your throttle kernel parameter and adjust sd_max_throttle if needed.
Learn about Linux
Download Linux
Get Linux help
Solaris settings
Posted by: Anonymous Coward on February 09, 2005 11:54 PMAnother thing You have to check - if MySQL does caching (most databases do - but don't know abut MySQL) is if Your FS block size matches DB cache block size. If Not You can init Your HFS filesystem with block size equal (or multiply) to DB block size (in case of oracle it speed up heavy IO operations 2-3 times).
And You can use forcedirectio mount option for data/index files (but only for these files!) - so You flush Your data without any OS caching and baypassing kernel. (In case of oracle is speed up IO operations by factor 4(!)).
Finally please check Your throttle kernel parameter and adjust sd_max_throttle if needed.
#