Il 07/12/2016 13:12, Carlos E. R. ha scritto:
On 2016-12-07 11:53, Martin Wilck wrote:
Rather than playing with tuning parameters, I'd suggest to proceed more systematically. Run some benchmarks to find out the "raw" performance of your disk for sequential and random IO. Do all this with the "noop" scheduler. I usually start out with a plain "dd" sequential read from the block device with 1M block size. If you have an unused partition, try sequential writes as well. Compare that to the device specs (or possibly with measurements you find on the net). This will give you an idea what to expect from the HW, and whether the HW is operating in the expected speed range. You can measure the raw read speed with hdparm -Tt /dev/DEVICE
Thanks to all replying to my question. Carlos, here you can see the result of the command you suggested: marco@linux-turion64:~> sudo hdparm -Tt /dev/sda [sudo] password di root: /dev/sda: Timing cached reads: 9168 MB in 2.00 seconds = 4585.57 MB/sec Timing buffered disk reads: 232 MB in 3.02 seconds = 76.71 MB/sec But I'm currently using the bfq scheduler which after some days of usage I can definetly affirm performs better than cfq with my system. Regards, -- Marco Calistri Opensuse Tumbleweed 64 bit Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 Intel® Sandybridge Mobile