Comment #2 on issue 15310 by robkroeger: Panning in Google Maps is slower in Chrome than in Safari and Firefox on Mac OS X http://code.google.com/p/chromium/issues/detail?id=15310
I would claim that Mac OS Chrome is generally slow to do screen updates compared to Safari. So, while V8 performance is competitive with squirrel fish extreme, the display subsystem seems to require sizably more CPU to achieve the same result as does Safari. As a simple specific example that makes this very clear, consider http://nerget.com/fluidSim/ The JavaScript code running in a render process uses ~90% of a single core and delivers performance equal or better to Safari4. However, the browser parent process also uses 85% of the cpu (MacBook pro) to update the display while Safari merely raises the Window server CPU load from ~3% to 7% to achieve the same result. Perhaps a way could be found to alter the renderer to (safely) write directly into the framebuffer? This would probably be good both for the <video> tag and would seem desirable to make O3D on chrome a viable gaming platform. -- 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 -~----------~----~----~----~------~----~------~--~---
