10% elapsed time regression on pyramid test


After the update to r55 the pyramid test is about 10% slower (56ms per frame instead of 51ms per frame).
We should look into what changed and try to optimize around it to get the numbers back down. Other tests aren't very stressful and so don't go above the 60Hz framerate before or after, but it is noticible on pyramid test.


nfurtwangler wrote Mar 31, 2010 at 8:44 AM

Brandon found that this is likely related to the extra alloc's per frame for the DynamicTree userData. The userData is an int, but it the field itself is an object so the int gets boxed.

Should be fixed by now, and we can verify by deploying to Xbox360 with before/after bits and running this test case.

wrote Feb 14, 2013 at 8:22 PM