anticipatory scheduling questions
Hello,
I have just installed 2.5.63-mm1 on my system and have been performing a very simple benchmarks. Here are my first results when compared against a RedHat 2.4.20-2.54 kernel:
(All times expressed as total times)
1. time dd if=/dev/zero of=/tmp/p bs=1024k count=256 2.5.63-mm1 -> 0m12.737s
2.4.20-2.54 -> 0m17.704s
2. time cp /tmp/p /tmp/q
2.5.63-mm1 -> 0m41.108s
2.4.20-2.54 -> 0m51.939s
3. time cmp /tmp/p /tmp/q
2.5.63-mm1 -> 1m7.349s
2.4.20-2.54 -> 0m58.966s
4. time cmp /dev/zero /tmp/q
2.5.63-mm1 -> 0m17.965s
2.4.20-2.54 -> 0m14.038s
The question is, why, apparently, is anticipatory scheduling perfomring worse than 2.4.20? Indeed, this can be tested interactively with an application like Evolution: I have configured Evolution to use 2 dictionaries (English and Spanish) for spell checking in e-mail messages. When running 2.4.20, if I choose to reply to a large message, it only takes a few seconds to read both dictionaries from disk and perform the spell checking. However, on 2.5.63-mm1 the same process takes considerably longer. Any reason for this?
Thanks!
Best regards,
Felipe Alfaro Solana
Signature · 5 lines
______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze
Quoted 11 lines · Felipe Alfaro Solana
Hello,
I have just installed 2.5.63-mm1 on my system and have been performing a very simple benchmarks. Here are my first results when compared against a RedHat 2.4.20-2.54 kernel:
(All times expressed as total times)
1. time dd if=/dev/zero of=/tmp/p bs=1024k count=256 2.5.63-mm1 -> 0m12.737s
2.4.20-2.54 -> 0m17.704s
It's hard to compare 2.4 and 2.5 on this one. 2.5 will start writing to disk much earlier, and that additional I/O can sometimes get in the way of other disk operations. The end result is that the test exits leaving more (or less) dirty data in memory and the time for writing that out is not accounted.
You need to either run a much longer test, or include a `sync' in the timings.
But in this case (assuming you're using ext3), the difference is probably explained by a timing fluke - the test on 2.4 kernel happened to cover three ext3 commit intervals while the 2.5 test squeezed itself into two.
Hard to say - there are a lot of variables here.
Quoted 3 lines
2. time cp
/tmp/p/tmp/q
2.5.63-mm1 -> 0m41.108s
2.4.20-2.54 -> 0m51.939s
Could be ext3 effects as well. Also maybe some differences in page aging implementations.
Quoted 3 lines
3. time cmp
/tmp/p/tmp/q
2.5.63-mm1 -> 1m7.349s
2.4.20-2.54 -> 0m58.966s
cmp needs to use a larger buffer ;)
Quoted 3 lines
4. time cmp
/dev/zero/tmp/q
2.5.63-mm1 -> 0m17.965s
2.4.20-2.54 -> 0m14.038s
Again, depends on how much of /tmp/q was left in pagecache.
Quoted 2 lines
The question is, why, apparently, is anticipatory scheduling perfomring worse than 2.4.20?
It doesn't seem to be from the above numbers?
Quoted 7 lines
Indeed, this can be tested interactively with an application like Evolution:
I have configured Evolution to use 2 dictionaries (English and Spanish) for spell checking in e-mail messages. When running 2.4.20, if I choose to reply to a large message, it only takes a few seconds to read both dictionaries from disk and perform the spell checking.
However, on 2.5.63-mm1 the same process takes considerably longer. Any reason for this?
Could you boot with elevator-deadline and retest?
How large are the dictionary files?