http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/jankometer.h?view=markup
On Thu, May 14, 2009 at 4:44 PM, Greg Spencer <[email protected]> wrote: > So, what is your nuanced definition of "Jank"? All it means to me is "bad". > Aren't all bugs bad? > -Greg. > > On Thu, May 14, 2009 at 2:44 PM, Linus Upson <[email protected]> wrote: >> >> I think this is important. I've been noticing the jank level rising as >> well. >> Linus >> >> On Wed, May 13, 2009 at 5:18 PM, Ben Goodger (Google) <[email protected]> >> wrote: >>> >>> Though I've upgraded my desktop PC to fancy hardware, I still use a >>> Core 2 Duo 2.4GHz laptop with 2GB RAM. This is still a pretty typical >>> configuration for even high end laptops today. Sad to say under heavy >>> load (several windows, many tabs in each), the amount of jank I'm >>> experiencing is pretty high. >>> >>> To help identify and triage these issues, I've added a "Jank" label in >>> the bug system. I feel like we should focus on reducing these issues >>> in the next release cycle - this is an area where we have historically >>> had a good performance, we should not lose it. >>> >>> It's hard to write tests for jankiness because time and entropy are >>> typically the key inputs more than any specific set of pages. But if >>> you experience jank in your own use of Chrome I encourage you to try >>> and identify causes and file bugs with this new label. >>> >>> http://code.google.com/p/chromium/issues/list?can=2&q=label%3AJank >>> >>> -Ben >>> >>> >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
