Linked by Thom Holwerda on Wed 19th Sep 2007 21:33 UTC, submitted by raoulduke
Permalink for comment 272697
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2007-09-19
Readahead and IO scheduler also make a lot of difference in performance. I don't use databases, only desktop, but I found useful performance tips in RedHat, Postgresql, and IBM documents. Right now I'm using JFS with the deadline IO scheduler and I'm impressed. It got even better after setting readahead to 1024.
Most database performance documents show that the deadline scheduler makes a lot of difference in throughput, and on benchmarks explicity using deadline JFS was almost allways the best. It's not EOL'd as some believe, last release is dated 2007-08-24.
Try this in any filesystem and you'll see the difference:
echo deadline > /sys/block/sda/queue/scheduler
echo 1024 > /sys/block/sda/queue/nr_requests
echo 250 > /sys/block/sda/queue/iosched/read_expire
Bruno