Comment #13 on issue 19268 by [email protected]: Throbbing takes a lot of CPU time http://code.google.com/p/chromium/issues/detail?id=19268
Some observations made in a small test app: * Running only an NSTimer at 30 fps needs about 1% cpu * Running the throbber animation in an empty window takes 3.2% cpu * Making the window textured takes this to 4% cpu * Embedding the throbber into a custom view that just `return;` in it's `drawRect:`increases this to 4.4% cpu * Giving that custom view the same drawing logic as tabview.mm (drawing gradients etc) increases this to 6.2% cpu Still not at the 10% cpu that chromium uses, but it looks a lot of the performance is used to composite the background layers of the 16x16 rect (window background is drawn for the square, completely overwritten by the tb view background which uses complex gradients, and then the png is blended on top of that). This takes time. -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
