All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Milton Miller <miltonm@bga.com>
Subject: Re: 82xx performance
Date: Thu, 17 Jul 2008 21:43:56 +0200	[thread overview]
Message-ID: <200807172143.57576.arnd@arndb.de> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B04B34D32@ismail.innsys.innovsys.com>

On Thursday 17 July 2008, Rune Torgersen wrote:
> Arnd Bergmann wrote:
> > Seeing more hits in handle_mm_fault suggests that you have
> > a higher page fault rate. A trivial reason for this might
> > be that the amount of memory was misdetected in the new
> > code (maybe broken device tree). What is the content of
> > /proc/meminfo after a fresh boot?
> Powerpc
> VmallocTotal:   474756 kB
> Ppc
> VmallocTotal:   245696 kB

This seems to be the only significant difference here, but
I don't see how it can make an impact on performance.

>         User time (seconds): 4339.11
>         User time (seconds): 4177.11

3.8% slowdown

>         System time (seconds): 319.41 
>         System time (seconds): 295.00

8.2% slowdown

>         Elapsed (wall clock) time (h:mm:ss or m:ss): 1:17:42
>         Elapsed (wall clock) time (h:mm:ss or m:ss): 1:14:35

4% slowdown

>         Minor (reclaiming a frame) page faults: 4213347
>         Minor (reclaiming a frame) page faults: 4203103

slightly more faults

>         Voluntary context switches: 53543
>         Voluntary context switches: 53812

This actually went down by 0.5%, both of these are well within
the expected 

>         Involuntary context switches: 90165
>         Involuntary context switches: 85856

4.8% more context switches, probably a side-effect of the longer
run-time.

So again, nothing conclusive. I'm running out of ideas.

	Arnd <><

  reply	other threads:[~2008-07-17 19:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 16:34 82xx performance Rune Torgersen
2008-07-14 20:44 ` Arnd Bergmann
2008-07-15 14:16   ` Rune Torgersen
2008-07-15 18:25   ` Rune Torgersen
2008-07-15 19:50     ` Arnd Bergmann
2008-07-16 21:08       ` Rune Torgersen
2008-07-16 21:45         ` Arnd Bergmann
2008-07-16 21:53           ` Rune Torgersen
2008-07-16 22:32             ` Arnd Bergmann
2008-07-17 15:12               ` Rune Torgersen
2008-07-17 15:47                 ` Arnd Bergmann
2008-07-17 15:52                   ` Rune Torgersen
2008-07-17 18:24                   ` Rune Torgersen
2008-07-17 19:43                     ` Arnd Bergmann [this message]
2008-07-17 19:54                       ` Rune Torgersen
2008-07-17 21:32                         ` Arnd Bergmann
2008-07-25 20:41                           ` Rune Torgersen
2008-07-26  3:47                             ` Milton Miller
2008-07-15 15:57 ` Milton Miller
2008-07-15 18:12   ` Rune Torgersen

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=200807172143.57576.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.