From: Ingo Molnar <mingo@elte.hu>
To: Colin Fowler <elethiomel@gmail.com>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Performance loss 2.6.22->22.6.23->2.6.24-rc7 on CPU intensive benchmark on 8 Core Xeon
Date: Wed, 16 Jan 2008 16:35:05 +0100 [thread overview]
Message-ID: <20080116153505.GB18553@elte.hu> (raw)
In-Reply-To: <cf3edd8d0801151505r54bfd9d0r89f57e3835f295e1@mail.gmail.com>
* Colin Fowler <elethiomel@gmail.com> wrote:
> > and context-switches 45K times a second. Do you know what is going
> > on there? I thought ray-tracing is something that can be
> > parallelized pretty efficiently, without having to contend and
> > schedule too much.
>
> This is a RTRT (real-time ray tracing) system and as a result differs
> from traditional offline ray-tracers as it is optimised for speed. The
> benchmark I ran while these data were collected renders an 80K polygon
> scene to a 512x512 buffer at just over 100fps.
>
> The context switches are most likely caused by the pthreads
> synchronisation code. There are two mutexs. Each job is a 32x32 tile
> and each mutex is therefore unlocked (512/32) * (512/32) * 100 (for
> 100fps) * 2 =~50k. There's very likely where our context switches are
> coming from. Larger tile sizes would of course reduce the locking
> overhead, but then the ray-tracer suffers form load imbalance as some
> tiles are much quicker to render than others. Empircally we've found
> that this tile-size works the best for us.
>
> The CPU idling occurs as the system doesn't yet perform asynchronous
> rendering. When all tiles in a current job queue are finished the
> current frame is done. At this point all worker threads sleep while
> the master thread blits the image to the screen and fills the job
> queue for the next frame. The data probably shows that one CPU is kept
> maxed and the others reach about 90% most of the time. This is
> something on my TODO list to fix along with a myriad of other
> optimisations :)
is this something i could run myself and see how it behaves with various
scheduler settings? (if yes, where can i download it and is there any
sample scene that would show similar effects.)
Ingo
next prev parent reply other threads:[~2008-01-16 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 17:37 Colin Fowler
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 [this message]
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=20080116153505.GB18553@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=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®