All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Mike Snitzer <snitzer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: dm perf scales poorly with 2.6.x kernel
Date: Thu, 17 Feb 2005 07:25:48 +0100	[thread overview]
Message-ID: <m14qgb3doz.fsf@muc.de> (raw)
In-Reply-To: <170fa0d20502161504f8db91b@mail.gmail.com> (Mike Snitzer's message of "Wed, 16 Feb 2005 16:04:57 -0700")

Mike Snitzer <snitzer@gmail.com> writes:
>
> Ultimately there appears to be a disproportionate increase in the DM
> performance hit as the IO throughput capability of the underlying
> block device increases (I'm obviously using a limited sampling so...).
>  But given the current results it is clear there will be a performance
> hit associated with using DM; but having that hit be fixed as the
> throughput scales would be ideal.

You could do a oprofile run to see where to CPU time is going to
and post the results.

-Andi

      reply	other threads:[~2005-02-17  6:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  4:08 dm perf scales poorly with 2.6.x kernel Mike Snitzer
2005-02-16 23:04 ` Fwd: " Mike Snitzer
2005-02-17  6:25   ` Andi Kleen [this message]

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=m14qgb3doz.fsf@muc.de \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@gmail.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.