linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Luigi Semenzato <semenzato@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Subject: Re: mm performance with zram
Date: Fri, 9 Jan 2015 08:45:59 -0800	[thread overview]
Message-ID: <CAA25o9SQfb3yO2D4ABeeYoZkurhxramAgckr9DVOG1=DwVF0qg@mail.gmail.com> (raw)
In-Reply-To: <20150108223024.da818218.akpm@linux-foundation.org>

On Thu, Jan 8, 2015 at 10:30 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Thu, 8 Jan 2015 14:49:45 -0800 Luigi Semenzato <semenzato@google.com> wrote:
>
>> I am taking a closer look at the performance of the Linux MM in the
>> context of heavy zram usage.  The bottom line is that there is
>> surprisingly high overhead (35-40%) from MM code other than
>> compression/decompression routines.
>
> Those images hurt my eyes.

Sorry about that.  I didn't find other ways of computing the
cumulative cost of functions (i.e. time spent in a function and all
its descendants, like in gprof).  I couldn't get perf to do that
either.  A flat profile shows most functions take a fracion of 1%, so
it's not useful.  If anybody knows a better way I'll be glad to use
it.

> Did you work out where the time is being spent?

No, unfortunately it's difficult to make sense of the graph profile as
well, especially with my low familiarity with the code.  There is a
surprising number of different callers into the heaviest nodes and I
cannot tell which paths correspond to which high-level actions.

--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-01-09 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 22:49 Luigi Semenzato
2015-01-09  6:30 ` Andrew Morton
2015-01-09 16:45   ` Luigi Semenzato [this message]
2015-01-10  0:06     ` Joonsoo Kim
2015-01-10  0:19       ` Luigi Semenzato
2015-01-10  0:42         ` Joonsoo Kim
2015-01-13  9:18 ` Vlastimil Babka
2015-01-13 16:25   ` Luigi Semenzato

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='CAA25o9SQfb3yO2D4ABeeYoZkurhxramAgckr9DVOG1=DwVF0qg@mail.gmail.com' \
    --to=semenzato@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.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