linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zlatko Calusic <zlatko@iskon.hr>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-mm@kvack.org
Subject: Re: pre2 swap_out() changes
Date: 13 Jan 2001 12:51:15 +0100	[thread overview]
Message-ID: <87y9wffz64.fsf@atlas.iskon.hr> (raw)
In-Reply-To: Linus Torvalds's message of "Fri, 12 Jan 2001 11:45:26 -0800 (PST)"

Linus Torvalds <torvalds@transmeta.com> writes:

> On 12 Jan 2001, Zlatko Calusic wrote:
> > 
> > Performance of 2.4.0-pre2 is terrible as it is now. There is a big
> > performance drop from 2.4.0. Simple test (that is not excessively
> > swapping, I remind) shows this:
> > 
> > 2.2.17     -> make -j32  392.49s user 47.87s system 168% cpu 4:21.13 total
> > 2.4.0      -> make -j32  389.59s user 31.29s system 182% cpu 3:50.24 total
> > 2.4.0-pre2 -> make -j32  393.32s user 138.20s system 129% cpu 6:51.82 total
> 
> Marcelo's patch (which is basically the pre2 mm changes - the other was
> the syntactic change of making "swap_cnt" be an argument to swap_out_mm()
> rather than being a per-mm thing) will improve feel for stuff that doesn't
> want to swap out - VM scanning is basically handled exclusively by kswapd,
> and it only triggers under low-mem circumstances.
> 

Hm, what I noticed is completely the opposite. pre2 seems a little bit
reluctant to swap out, and when it does it looks like it picks wrong
pages. During the compile sessions (results above) pre2 had long
periods where it just tried to get its working set in memory and
during that time all 32 processes were on hold. Thus only 129% CPU
usage and much longer total time.

On the other hand, 2.4.0 + Marcelo kept both processors busy at all
times. Sometimes only few processes were TASK_RUNNING, but the system
_never_ got in the situation where it had spare unused CPU cycles.

If I start typical make -j2 compile my %CPU time is also 182% or 183%,
so 2.4.0 was _really_ good.
-- 
Zlatko
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  parent reply	other threads:[~2001-01-13 11:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 10:38 Marcelo Tosatti
2001-01-11 18:49 ` Linus Torvalds
2001-01-12 11:35   ` Zlatko Calusic
2001-01-12 19:45     ` Linus Torvalds
2001-01-12 19:22       ` Marcelo Tosatti
2001-01-13  0:23         ` Linus Torvalds
2001-01-12 22:41           ` Marcelo Tosatti
2001-01-13  0:45             ` Linus Torvalds
2001-01-17  7:05             ` Rik van Riel
2001-01-18 11:54           ` Rik van Riel
2001-01-13 11:41         ` Zlatko Calusic
2001-01-17  7:08           ` Rik van Riel
2001-01-13 11:51       ` Zlatko Calusic [this message]
2001-01-14  2:39         ` Marcelo Tosatti
2001-01-14  4:36           ` Linus Torvalds
2001-01-14  3:50             ` Marcelo Tosatti
2001-01-14 15:51               ` Ed Tomlinson
2001-01-14 14:13                 ` Marcelo Tosatti
2001-01-14 16:15                   ` Zlatko Calusic
2001-01-14 17:22                     ` Zlatko Calusic
2001-01-17  7:16                       ` Rik van Riel
2001-01-17  7:15                 ` Rik van Riel
2001-01-17  7:12               ` Rik van Riel
2001-01-11 20:52 Benjamin Redelings I

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=87y9wffz64.fsf@atlas.iskon.hr \
    --to=zlatko@iskon.hr \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    --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