<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=95474#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1" href="https://bugs.freedesktop.org/show_bug.cgi?id=95474">bug 95474</a> from <a class="email" href="mailto:maraeo@gmail.com" title="Marek Olšák <maraeo@gmail.com>"> Marek Olšák</a> <pre>(In reply to Jan Ziak from <a href="show_bug.cgi?id=95474#c9">comment #9</a>) > Created <a href="attachment.cgi?id=124063" name="attach_124063" title="kcachegrind screenshot: _mesa_FenceSync">attachment 124063</a> <a href="attachment.cgi?id=124063&action=edit" title="kcachegrind screenshot: _mesa_FenceSync">[details]</a> > kcachegrind screenshot: _mesa_FenceSync > > I ran callgrind on Bioshock with mesa-git. > > Callgrind instrumentation was enabled only when the Bioshock benchmark was > rendering frames from the game. The benchmark graphics quality was set to > Medium. > > The screenshot I am sending indicates that Bioshock expects a faster > _mesa_FenceSync implementation. I wouldn't trust callgrind, because it runs on a CPU emulator. The proper way to profile this is to build Mesa with -fno-omit-frame-pointer and use sysprof, which is very easy to use. Sysprof can also save the results to disk.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>