public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
To: akpm@digeo.com, "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: anticipatory scheduling questions
Date: Sat, 01 Mar 2003 00:12:20 +0100	[thread overview]
Message-ID: <20030228231220.19048.qmail@linuxmail.org> (raw)

----- Original Message ----- 
From: Andrew Morton <akpm@digeo.com> 
Date: Fri, 28 Feb 2003 11:14:18 -0800 
To: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org> 
Subject: Re: anticipatory scheduling questions 
 
> "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org> wrote: 
> > 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? 
>  
> > > 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? 
-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

             reply	other threads:[~2003-02-28 23:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28 23:12 Felipe Alfaro Solana [this message]
2003-02-28 23:16 ` anticipatory scheduling questions Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2003-03-02 21:50 Felipe Alfaro Solana
2003-03-02 11:40 Felipe Alfaro Solana
2003-03-02 20:43 ` Andrew Morton
2003-03-01 14:48 Felipe Alfaro Solana
     [not found] <fa.g5ol5kg.cgoq0g@ifi.uio.no>
     [not found] ` <fa.hp882fv.1u0orj9@ifi.uio.no>
2003-03-01 12:48   ` Ed Tomlinson
2003-03-01 10:25 Felipe Alfaro Solana
2003-03-01 10:40 ` Andrew Morton
2003-03-01 11:51   ` David Lang
2003-03-01 17:15     ` Alan Cox
2003-02-28 14:38 Felipe Alfaro Solana
2003-02-28 19:14 ` Andrew Morton
2003-02-28 12:18 Felipe Alfaro Solana
2003-02-28 12:44 ` Andrew Morton
2003-02-27 22:24 Felipe Alfaro Solana
2003-02-27 23:26 ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030228231220.19048.qmail@linuxmail.org \
    --to=felipe_alfaro@linuxmail.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox