Skip to contentSkip to conversation

anticipatory scheduling questions

DISCUSSION Felipe Alfaro Solana 2 participants 2 messages Feb 28, 2003

lore
Share & tools
lore
#0 lore raw

----- Original Message -----
From: Andrew Morton <[email protected]>
Date: Fri, 28 Feb 2003 11:14:18 -0800
To: "Felipe Alfaro Solana" <[email protected]>
Subject: Re: anticipatory scheduling questions

Quoted 12 lines
Quoted 4 lines · Felipe Alfaro Solana

I have done so: Evolution is a complex application with many interdependencies and is not very prone to launch diagnostic messages to the console. Anyways, I haven't seen any diagnostic message in the console. I still think there is something in the AS I/O scheduler that is not working at full read throughput. Of course I'm no expert.

It certainly does appear that way. But you observed the same runtime with the deadline scheduler. Or was that a typo?

Quoted 3 lines
Quoted 3 lines

2.4.20-2.54 -> 9s
2.5.63-mm1 w/Deadline -> 34s
2.5.63-mm1 w/AS -> 33s

It wasn't a typo... In fact, both deadline and AS give roughly the same timings (one second up or down). But I still don't understand why 2.5 is performing so much worse than 2.4. Could a "vmstat" or "iostat" dump be interesting?

Signature · 5 lines
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze
#1 lore raw
Quoted 16 lines · Felipe Alfaro Solana

----- Original Message -----
From: Andrew Morton <[email protected]>
Date: Fri, 28 Feb 2003 11:14:18 -0800
To: "Felipe Alfaro Solana" <[email protected]>
Subject: Re: anticipatory scheduling questions

Quoted 9 lines
Quoted 4 lines · Felipe Alfaro Solana

I have done so: Evolution is a complex application with many interdependencies and is not very prone to launch diagnostic messages to the console. Anyways, I haven't seen any diagnostic message in the console. I still think there is something in the AS I/O scheduler that is not working at full read throughput. Of course I'm no expert.

It certainly does appear that way. But you observed the same runtime with the deadline scheduler. Or was that a typo?

Quoted 7 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

2.4.20-2.54 -> 9s
2.5.63-mm1 w/Deadline -> 34s
2.5.63-mm1 w/AS -> 33s

It wasn't a typo... In fact, both deadline and AS give roughly the same timings (one second up or down). But I
still don't understand why 2.5 is performing so much worse than 2.4.

Me either. It's a bug.

Does basic 2.5.63 do the same thing? Do you have a feel for when it started happening?

Quoted 1 line

Could a "vmstat" or "iostat" dump be interesting?

2.4 versus 2.5 would be interesting, yes.