public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Thomas Richter <richter@rus.uni-stuttgart.de>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Performance drop on XDrawRectangles()
Date: Wed, 08 Jan 2014 18:49:40 +0100	[thread overview]
Message-ID: <52CD8FB4.9030806@rus.uni-stuttgart.de> (raw)
In-Reply-To: <20140108171047.GB27406@nuc-i3427.alporthouse.com>

On 01/08/2014 06:10 PM, Chris Wilson wrote:
> On Wed, Jan 08, 2014 at 04:57:52PM +0100, Thomas Richter wrote:
>> Hi folks,
>>
>> during the changes from 3.12rc7 to 3.13rc4, the performance of
>> XDrawRectangles() dropped considerably. Interestingly, it is not the
>> raw rectangles drawing operations that are slow, but it seems that
>> the "per-call" overhead has increased by one magnitude. In specific,
>> if you use the unmodified "x11pref" program:
>>
>
> Just to be clear: new = 3.13-rc4, old = 3.12-rc7 ?

Yes, exactly.

> I've taken a quick look at this on an ivb i7-3270qm, and see a 296kops/s
> to 248kops/s decrease. Not massive, and considering the difference in
> our hardware probably a distinct issue.

Well, note that a 1Ghz P-III / i830M is not an i7-3270qm. (-;

Did you made the changes in x11perf as I did? The bottleneck is not in 
the actual rectangle rendering, it is somewhere in the call-path from 
the application down to the hardware, i.e. the per-call overhead 
increased by a factor of eight.

Kernel configuration is identical, as much as I could arrange it. X11 
and higher level libraries are all identical, I only changed the kernel.

Greetings,
	Thomas

  reply	other threads:[~2014-01-08 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 15:57 Performance drop on XDrawRectangles() Thomas Richter
2014-01-08 16:18 ` Daniel Vetter
2014-01-08 17:10 ` Chris Wilson
2014-01-08 17:49   ` Thomas Richter [this message]
2014-01-08 18:09     ` Chris Wilson
2014-01-08 22:08       ` Chris Wilson

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=52CD8FB4.9030806@rus.uni-stuttgart.de \
    --to=richter@rus.uni-stuttgart.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox