dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 51787] performance regression with llvm shader compiler in ut2004
Date: Thu, 02 Aug 2012 22:32:43 +0000	[thread overview]
Message-ID: <bug-51787-502-wsJ0xWM0gg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-51787-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=51787

--- Comment #3 from Andy Furniss <lists@andyfurniss.entadsl.com> 2012-08-02 22:32:43 UTC ---
(In reply to comment #2)
> It might not help in fixing this, but I found that the framerate is much more
> consistent if I load all cpu cores with something while playing ut2004.
> Normally, the framerate counter is green, but flashes into yellow and purple,
> which makes movements very choppy. When something is running in the background,
> the framerate counter stays green, and all movements are smooth.

Maybe cpufreq is causing this here's what I get on the demo on an HD4890 +
4x3.4GHz phenom II.

R600_LLVM=0 ut2004
as-convoy?spectatoronly=1?numbots=8?quickstart=1?attractcam=1 -benchmark
-seconds=120 -nosound

cpufreq ondemand - 

30.027578 / 76.497787 / 162.457611 fps

cpufreq set to performance

37.627441 / 93.523949 / 197.051376 fps

> 
> With the llvm compiler the game is unplayable either way.

I see the stalling in the demo benchmark.

2.030273 / 70.589706 / 196.047073 fps

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-08-02 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 14:03 [Bug 51787] New: performance regression with llvm shader compiler in ut2004 bugzilla-daemon
2012-07-06 15:25 ` [Bug 51787] " bugzilla-daemon
2012-08-02 22:04 ` bugzilla-daemon
2012-08-02 22:32 ` bugzilla-daemon [this message]
2012-11-01 18:17 ` bugzilla-daemon
2012-11-01 20:12 ` bugzilla-daemon
2013-05-06 23:26 ` bugzilla-daemon
2019-09-18 19:00 ` bugzilla-daemon

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=bug-51787-502-wsJ0xWM0gg@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).