From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: X11 performance regressions
Date: Mon, 09 May 2011 22:43:41 +0100 [thread overview]
Message-ID: <15db10$kicfca@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <4DC6DF5D.2050006@t-online.de>
As a point of comparison, here are the similar results with master of all
the various trees on my 1.6GHz N450 (Atom+PineView) [so not strictly an
apples-to-apples comparison, your CPU is about 4-5x faster, but PNV is
about 3-4x faster than the 915GM (clock-for-clock)]:
On Sun, 08 May 2011 20:22:21 +0200, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> 10000000 trep @ 0.0032 msec (309000.0/sec): Dot
> 40000000 trep @ 0.0006 msec (1650000.0/sec): Dot
50000000 trep @ 0.0005 msec (1830000.0/sec): Dot
*100000000 trep @ 0.0003 msec (2900000.0/sec): Dot
> 45000 trep @ 0.5973 msec ( 1670.0/sec): 500x500 rectangle
> 100000 trep @ 0.4282 msec ( 2340.0/sec): 500x500 rectangle
100000 trep @ 0.3210 msec ( 3120.0/sec): 500x500 rectangle
> 2000000 reps @ 0.0034 msec (296000.0/sec): 1x1 stippled rectangle (8x8 stipple)
> 8000000 reps @ 0.0007 msec (1420000.0/sec): 1x1 stippled rectangle (8x8 stipple)
25000000 trep @ 0.0011 msec (902000.0/sec): 1x1 stippled rectangle (8x8 stipple)
*30000000 trep @ 0.0008 msec (1180000.0/sec): 1x1 stippled rectangle (8x8 stipple)
> 1500 trep @ 22.4602 msec ( 44.5/sec): 500x500 stippled rectangle (8x8 stipple)
> 3000 trep @ 9.2680 msec ( 108.0/sec): 500x500 stippled rectangle (8x8 stipple)
4000 trep @ 6.8986 msec ( 145.0/sec): 500x500 stippled rectangle (8x8 stipple)
*3500 trep @ 7.0786 msec ( 141.0/sec): 500x500 stippled rectangle (8x8 stipple)
> 100000 trep @ 0.4043 msec ( 2470.0/sec): Fill 10x10 trapezoid
> 1000000 trep @ 0.0336 msec ( 29700.0/sec): Fill 10x10 trapezoid
2000000 trep @ 0.0152 msec ( 65700.0/sec): Fill 10x10 trapezoid
*4000000 trep @ 0.0064 msec (156000.0/sec): Fill 10x10 trapezoid
Hmm. My suspicion was that this was GEM-related regressions (the overhead
of dynamic buffer manager and relocations) along with various
optimizations for the common cases affecting the software fallback
dominated benchmarks selected above. And whilst there may some element of
that behind the regression you're observing, I don't think that is the
whole story and Adam is right to suggest to check that the systems are
indeed configured identically (wrt to debug and optimisation options).
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-05-09 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:22 X11 performance regressions Knut Petersen
2011-05-09 16:53 ` Adam Jackson
2011-05-09 21:43 ` Chris Wilson [this message]
2011-05-11 14:46 ` Knut Petersen
2011-05-11 17:52 ` Chris Wilson
2011-05-12 7:19 ` Knut Petersen
2011-05-12 7:38 ` Chris Wilson
2011-05-12 8:24 ` Knut Petersen
2011-05-12 8:55 ` Chris Wilson
2011-05-12 9:34 ` Knut Petersen
2011-05-13 9:24 ` Knut Petersen
2011-05-11 19:49 ` Adam Jackson
2011-05-11 21:22 ` Knut Petersen
2011-05-12 13:42 ` Adam Jackson
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='15db10$kicfca@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Knut_Petersen@t-online.de \
--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.