On Tuesday, April 08, 2014 18:42:47 Michel Dänzer wrote: > I was away for the last two weeks, and when I came back I noticed that > gpu.py is now taking around 20 minutes to complete, whereas it only took > around 10 minutes before. I was able to bisect this to: > > > 26326d4032631cdb4eb6816aada6c81db6f186d7 is the first bad commit > commit 26326d4032631cdb4eb6816aada6c81db6f186d7 > Author: Dylan Baker <baker.dyla...@gmail.com> > Date: Wed Feb 5 15:44:37 2014 -0800 > > framework/shader_test.py: simplify ShaderTest > > > This is on an A10-7850K (quad core Kaveri) APU FWIW.
testing with 26326d4032631cdb4eb6816aada6c81db6f186d7~ and master, using the -c option, the -1 option, and no concurrency control: I don't have access to an APU, but on my IvyBridge i5-3320M dual-core + HT (4 total threads) the times I'm seeing very little difference between runs, master seems to be running negligibly faster, my BayTrail N2830 also shows very similar numbers, with master being very slightly faster. -Dylan
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Piglit mailing list Piglit@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/piglit
