anticipatory scheduling questions
----- Original Message -----
From: Andrew Morton <[email protected]>
Date: Thu, 27 Feb 2003 15:26:04 -0800
To: "Felipe Alfaro Solana" <[email protected]>
Subject: Re: anticipatory scheduling questions
Quoted 10 lines
Quoted 7 lines · Felipe Alfaro Solana
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?
I have done benchmark tests with Evolution under the following conditions: (times measured since the reply button is clicked until the message is opened)
2.4.20-2.54 -> 9s
2.5.63-mm1 w/Deadline -> 34s
2.5.63-mm1 w/AS -> 33s
The 2.4.20-2.54 is *not* a stock kernel, but Red Hat's own patched kernel (I think they include most of Alan Cox patches). Times are measured manually (don't know how to "time" the time elapsed since I click a button and the reply window is opened). Also, the filesystem is "ext2" running on a laptop (not a really fast hard disk).
Quoted 1 line
How large are the dictionary files?
Well, the aspell dictionary files are roughly 16MB for the Spanish dictionary and 4MB for the English one.
Signature · 5 lines
______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze
Quoted 8 lines · Felipe Alfaro Solana
I have done benchmark tests with Evolution under the following conditions:
(times measured since the reply button is clicked until the message is opened)2.4.20-2.54 -> 9s
2.5.63-mm1 w/Deadline -> 34s
2.5.63-mm1 w/AS -> 33s
Well something has gone quite wrong there. It sounds as if something in
the 2.5 kernel has broken evolution.
Does this happen every time you reply to a message or just the first time?
And if you reply to a message, then quit evolution, then restart evolution then reply to another message, does the same delay happen?
The above tests will eliminate the IO system at least.
If the delay is still there when all the needed datais in pagecache then please run `vmstat 1' during the operation and send the part of the trace from the period when the delay happens.
I'd suggest that you launch evolution from the command line in an xterm so you can watch for any diagnostic messages.
Thanks.