linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Paolo Ciarrocchi <ciarrocchi@linuxmail.org>
Cc: vda@port.imtp.ilyichevsk.odessa.ua, conma@kolivas.net,
	riel@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: Poor performance with 2.5.52, load and process in D state
Date: Wed, 25 Dec 2002 23:44:08 -0800	[thread overview]
Message-ID: <3E0AB348.7EC3D454@digeo.com> (raw)
In-Reply-To: 20021226000308.31344.qmail@linuxmail.org

Paolo Ciarrocchi wrote:
> 
> Hi Andrew/Rik/Con/all
> 
> Andrew, I promised you to run a few tests
> using osdb (www.osdb.org with 40M of data)against both
> 2.4.19 and 2.5.52 booting the kernel with the
> mem=XXM paramter.
> 
> I also played with the /proc/sys/vm/swappiness
> parameter, I've ran all the tests with the standard
> swappiness value (60), with 80 and 100.
> 
> 100 means the 2.4 behaviour, isn't it ?

Not really.  swappiness=100 is strict LRU, treating pagecache and
mapped-into-process-memory pages identically.  Smaller values will
make the kernel prefer to preserve mapped-into-process-memory.

> Looking at the results it seems that the "standard"
> value is too low, probably 80 is the best one.
> What do you think ?

I would agree with that.
 
> ...
> 
> 2.4.19  all     x               778.65 seconds  (0:12:58.65)
> 2.5.52  all     60              768.98 seconds  (0:12:48.98)
> 2.5.52  all     80              770.43 seconds  (0:12:50.43)
> 2.5.52  all     100             771.76 seconds  (0:12:51.76)

Only 1% difference.  On my 4xPIII with mem=128M, 2.4.20-pre2 took
1080.55 seconds and 2.5.52-mm3 took 991.03.  That's 9% faster, and
from the profile:

c010a858 system_call                                 192   4.3636
c011e518 current_kernel_time                         201   3.3500
c012cdbc __generic_file_aio_read                     214   0.4652
c012bba0 kallsyms_lookup                             219   0.8295
c012ccec file_read_actor                             230   1.1058
c0145abc fget                                        318   4.1842
c01d3ed4 radix_tree_lookup                           384   3.8400
c0144be0 vfs_read                                    409   1.3279
c01315f4 check_poison_obj                            695   7.8977
c012c964 do_generic_mapping_read                    1007   1.1988
c01d7ae0 __copy_user_intel                         34130 213.3125
c0108a58 poll_idle                                299231 3562.2738

it appears that this benefit came from the special usercopy code.
What sort of CPU are you using?

  reply	other threads:[~2002-12-26  7:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26  0:03 Poor performance with 2.5.52, load and process in D state Paolo Ciarrocchi
2002-12-26  7:44 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-26  9:45 Paolo Ciarrocchi
2002-12-26  9:26 Paolo Ciarrocchi
2002-12-26  9:34 ` Andrew Morton
2002-12-23 12:44 Paolo Ciarrocchi
2002-12-22 17:09 Paolo Ciarrocchi
2002-12-22 11:37 Paolo Ciarrocchi
2002-12-23 11:29 ` Andrew Morton
2002-12-25 13:12   ` Denis Vlasenko
2002-12-25  8:41     ` 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=3E0AB348.7EC3D454@digeo.com \
    --to=akpm@digeo.com \
    --cc=ciarrocchi@linuxmail.org \
    --cc=conma@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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;
as well as URLs for NNTP newsgroup(s).