<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [g965 Regression bisected] Performance regression and piglit assertions due to liveness analysis" href="https://bugs.freedesktop.org/show_bug.cgi?id=92744#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [g965 Regression bisected] Performance regression and piglit assertions due to liveness analysis" href="https://bugs.freedesktop.org/show_bug.cgi?id=92744">bug 92744</a> from <a class="email" href="mailto:mattst88@gmail.com" title="Matt Turner <mattst88@gmail.com>"> Matt Turner</a> <pre>(In reply to Ian Romanick from <a href="show_bug.cgi?id=92744#c3">comment #3</a>) > I suspect it hurts the g965 machines more because they're just slower CPUs. > Since the overhead /should/ just be added in app (or test) start up time (as > opposed to during rendering), I wouldn't worry about it too much. It affects (affected) piglit. Piglit runtime on i965 on Jenkins went from 9 minutes to 33, noticeably slowing down overall Jenkins runtimes. It seems to be fixed now, presumably by Connor's patch that fixed the assertion failure. Would be interesting to understand more what was going on. I'll let Mark confirm and close the bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>