mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Colin Fowler" <elethiomel@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Performance loss 2.6.22->22.6.23->2.6.24-rc7 on CPU intensive benchmark on 8 Core Xeon
Date: Mon, 14 Jan 2008 17:37:21 +0000	[thread overview]
Message-ID: <cf3edd8d0801140937w755c3e75me83c214ebc1f4cd3@mail.gmail.com> (raw)

Please CC me as I'm not subscribed.

I have (what is to me) a strange and very repeatable slowdown for a
CPU intensive benchmark on my system  on newer kernels.

Hardware : Dell Precision 470.
CPU 2x2.0GHz Quad Core Xeon E5335 CPUs
Memory 4GB ECC RAM.
OS Ubuntu x86_64 7.10 (Gutsy Gibbon)
Compiler : gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)

Benchmark : A ray-trace is performed on 500 times on 17 separate
scenes. Workload is distributed by tiling the framebuffer into N 32x32
pixel tiles. Each CPU grabs one of N tiles out of the queue and
repeats until no jobs are left. Rendering is to a shared framebuffer
(obviously this causes problems with caching). Locking and
synchronization is done using pthreads.

Other details: The system is cleanly booted for each run. No I/O is
performed during the timed portions of the test. The benchmark does
however read a model file from the drive and build a data structure
from it before each timed portion.


On the 2.6.22 series of kernels results are pretty much the same. On
2.6.23 series kernels I see a loss in speed of ~2% across the board.
On 2.6.24-rc7 that loss in speed is perhaps very slightly worse (~3%).
2.6.22 Kernels tested: 22.9(Ubuntu Stock Kernel), 22.14, 22.15
2.6.23 Kernels tested: 23.1, 23.3,  23.13
2.6.24 Kernels tested: 24-rc7

I have my kernel compiled to use the SLAB allocator. All other
tweaking options are set as defaults. My config files are available at
http://vangogh.cs.tcd.ie/fowler/configs  . Perhaps I'm configuring
something wrong for the type of work I do?

regards,
        Colin

             reply	other threads:[~2008-01-14 17:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 17:37 Colin Fowler [this message]
2008-01-14 18:55 ` Ingo Molnar
2008-01-14 22:42   ` Colin Fowler
2008-01-14 22:43     ` Colin Fowler
2008-01-15 17:01     ` Colin Fowler
2008-01-15 22:06       ` Ingo Molnar
2008-01-15 23:05         ` Colin Fowler
2008-01-16 15:35           ` Ingo Molnar
2008-01-16 16:10             ` Colin Fowler
2008-01-16 16:19               ` Ingo Molnar
2008-01-16 16:38                 ` Colin Fowler
2008-01-16 17:34         ` Colin Fowler
2008-01-18 10:55           ` Ingo Molnar

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=cf3edd8d0801140937w755c3e75me83c214ebc1f4cd3@mail.gmail.com \
    --to=elethiomel@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®