All of lore.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: X11 performance regressions
Date: Sun, 08 May 2011 20:22:21 +0200	[thread overview]
Message-ID: <4DC6DF5D.2050006@t-online.de> (raw)

I compared the performance of X11 on two otherwise idle machines.

Hardware
========
Both have
identical mainboards (Aopen i915GMm-hfs),
identical memory and BIOS setup.
Both cpus are Intel Pentium M mobile (Dothan).
One runs at 1.86 Mhz, the other runs at 2.00 MHz

Software
=======
1.86 MHz system:
opensuse 11.2
X.Org X Server 1.6.5
Release Date: 2009-10-11
kernel 2.6.38.5

2.00 MHz system:
opensuse 11.4
X.Org X Server 1.10.99
git-tree, 2011-may-7
kernel 2.6.39-rc4-drm-intel-staging

x11perf results
===========

The first line always gives the test result of the 2.00 Mhz system with the current Xorg,
the second line gives the test result of the 1.86 MHz sytem with Xorg 1.6.5. Read a
few representative examples:

10000000 trep @   0.0032 msec (309000.0/sec): Dot
40000000 trep @   0.0006 msec (1650000.0/sec): Dot

  45000 trep @   0.5973 msec (  1670.0/sec): 500x500 rectangle
 100000 trep @   0.4282 msec (  2340.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)

   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)

 100000 trep @   0.4043 msec (  2470.0/sec): Fill 10x10 trapezoid
1000000 trep @   0.0336 msec ( 29700.0/sec): Fill 10x10 trapezoid

The old X on the PC with the slower cpu is always significantly faster than the current git code,
very often more than 5 times as fast, and a number of test show 1.6.5 to be more than 12 times
faster than 1.10.99.

I did not use any special configuration options at compile time
1.10.99 was built using the following commands.

export PREFIX=/home/knut/local
export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig
export PATH=$PREFIX/bin:$PATH
export ACLOCAL="aclocal -I $PREFIX/share/aclocal"
export LD_LIBRARY_PATH=$PREFIX/lib
export PYTHONPATH=$PREFIX/lib/python2.7/site-packages
util/modular/build.sh -g $PREFIX

Could anybody please explain why the old server is so much faster?
Are there any compile time or runtime options that could/should be used?

cu,
 Knut

             reply	other threads:[~2011-05-08 18:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 18:22 Knut Petersen [this message]
2011-05-09 16:53 ` X11 performance regressions Adam Jackson
2011-05-09 21:43 ` Chris Wilson
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=4DC6DF5D.2050006@t-online.de \
    --to=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.