All of lore.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Performance regression, please revert commit 441ef916ae6569c88b3d6abaf7fea4d69be49d76
Date: Sun, 13 Jan 2013 11:09:38 +0100	[thread overview]
Message-ID: <50F287E2.9030709@t-online.de> (raw)

There is a massive performance regression on i915GM hardware,
opening/closing/redrawing looks as if it is done in slow motion.

I bisected the problem to:

commit 441ef916ae6569c88b3d6abaf7fea4d69be49d76
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Jan 10 19:14:21 2013 +0000

     intel: Throttle harder

     Filling the rings is a very unpleasant user experience, so cap the
     number of batches we allow to be inflight at any one time.

     Interestingly, as also found with SNA, throttling can improve
     performance by reducing RSS. However, typically throughput is improved
     (at the expense of latency) by oversubscribing work to the GPU and a
     10-20% slowdown is commonplace for cairo-traces. Notably, x11perf is
     less affected and in particular application level benchmarks show no
     change.

     Note that this exposes another bug in libdrm-intel 2.4.40 on gen2/3.

     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Please revert 441ef (or limit the new code to hardware that benefits from it)

cu,
  Knut

             reply	other threads:[~2013-01-13 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13 10:09 Knut Petersen [this message]
2013-01-13 10:23 ` Performance regression, please revert commit 441ef916ae6569c88b3d6abaf7fea4d69be49d76 Chris Wilson
2013-01-13 10:35   ` Knut Petersen
2013-01-13 10:50     ` Chris Wilson
2013-01-13 16:42       ` Knut Petersen

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=50F287E2.9030709@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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 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.