Issue 3328: DHTML perf test should not depend on timer clamping
http://code.google.com/p/chromium/issues/detail?id=3328
New issue report by [EMAIL PROTECTED]:
Raising the setTimeout() clamp caused a huge loss in the DHTML perf test.
This is worrisome, as it means a major component of what the test is
measuring is the time spent waiting for these, which I don't think the test
was intended to do. Now a regression of the same absolute magnitude will
cause a smaller proportional loss on the test and be hard to notice. We
should rewrite the test to not care about setTimeout() clamping.
Issue attributes:
Status: Untriaged
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-2 OS-All Area-DevTools
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
