From: Lorenzo Allegrucci <lenstra@tiscalinet.it>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: torvalds@transmeta.com, riel@conectiva.com.br,
linux-kernel@vger.kernel.org
Subject: Re: new OOM heuristic failure (was: Re: VM: qsbench)
Date: Fri, 02 Nov 2001 18:36:50 +0100 [thread overview]
Message-ID: <3.0.6.32.20011102183650.02007100@pop.tiscalinet.it> (raw)
In-Reply-To: <20011102140001.7c995186.skraw@ithnet.com>
In-Reply-To: <3.0.6.32.20011031185529.01fc4310@pop.tiscalinet.it> <Pine.LNX.4.33L.0110311259570.2963-100000@imladris.surriel.com> <3.0.6.32.20011031185529.01fc4310@pop.tiscalinet.it>
At 14.00 02/11/01 +0100, Stephan von Krawczynski wrote:
>Hello Lorenzo,
>
>please find attached next vmscan.c patch which sums up the delayed swap_out
>(first patch), the fix for not swapping when nr_pages is reached, and (new) the
>idea to swap more pages in one call to swap_out if priority gets higher.
>
>I have not the slightest idea what all this does to the performance. Especially
>the "more" swap_out code is a pure try-and-error type of thing. Can you do some
>testing please?
vmscan-patch2 looks slightly slower than vmscan-patch:
lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
70.800u 2.210s 2:27.96 49.3% 0+0k 0+0io 18551pf+0w
lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
70.600u 2.150s 2:28.49 48.9% 0+0k 0+0io 18728pf+0w
lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
70.690u 2.080s 2:28.77 48.9% 0+0k 0+0io 18753pf+0w
1:03 kswapd
Same test with 400M of swap:
lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
72.180u 2.110s 2:31.37 49.0% 0+0k 0+0io 18696pf+0w
lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
70.400u 2.200s 2:31.04 48.0% 0+0k 0+0io 18940pf+0w
lenstra:~/src/qsort> time ./qsbench -n 90000000 -p 1 -s 140175100
70.950u 2.210s 2:32.35 48.0% 0+0k 0+0io 19115pf+0w
1:02 kswapd
kswapd still takes many cycles.
--
Lorenzo
next prev parent reply other threads:[~2001-11-02 17:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 12:12 VM: qsbench Lorenzo Allegrucci
2001-10-31 12:23 ` Jeff Garzik
2001-10-31 15:00 ` new OOM heuristic failure (was: Re: VM: qsbench) Rik van Riel
2001-10-31 15:52 ` Linus Torvalds
2001-10-31 16:04 ` Rik van Riel
2001-10-31 17:42 ` Stephan von Krawczynski
2001-10-31 18:22 ` Linus Torvalds
2001-10-31 17:55 ` Lorenzo Allegrucci
2001-10-31 18:06 ` Linus Torvalds
2001-10-31 21:31 ` Lorenzo Allegrucci
2001-11-02 13:00 ` Stephan von Krawczynski
2001-11-02 17:36 ` Lorenzo Allegrucci [this message]
2001-10-31 17:55 ` VM: qsbench Lorenzo Allegrucci
[not found] <Pine.LNX.3.96.1011031133645.448B-100000@gollum.norang.ca>
2001-10-31 19:46 ` new OOM heuristic failure (was: Re: VM: qsbench) Linus Torvalds
[not found] <200111012108.WAA28044@webserver.ithnet.com>
[not found] ` <3.0.6.32.20011101214957.01feaa70@pop.tiscalinet.it>
2001-11-01 21:59 ` Lorenzo Allegrucci
2001-11-01 23:35 ` Stephan von Krawczynski
2001-11-02 0:37 ` Linus Torvalds
2001-11-02 2:17 ` Stephan von Krawczynski
2001-11-02 2:21 ` Linus Torvalds
2001-11-02 2:30 ` Stephan von Krawczynski
2001-11-02 2:55 ` Stephan von Krawczynski
2001-11-02 2:37 Ed Tomlinson
2001-11-02 3:01 ` Stephan von Krawczynski
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=3.0.6.32.20011102183650.02007100@pop.tiscalinet.it \
--to=lenstra@tiscalinet.it \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=skraw@ithnet.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®