A game changer for interactive performance.
Monday, November 21, 2011
Labels: v8
Today we are announcing the release of Chrome’s new incremental garbage collector (GC) which dramatically improves interactive performance of web apps and HTML5 games.
The V8 project has made huge progress improving peak performance of web apps. With the advent of technologies like WebGL we’re seeing the emergence of highly interactive and graphically intensive apps, such as the new version of Google Maps, new games and demos. But with these new uses comes a need for better interactive performance in JavaScript.
Avoiding pauses is vital to achieving good interactive performance. Previously, garbage collection pause times depended on the amount of memory used. Therefore, large interactive apps were impacted by pauses that caused hiccuping. V8’s new GC reduces pause times dramatically while maintaining great peak performance and memory use.
To evaluate the new GC, we took the most memory intensive peak performance test from the V8 Benchmark Suite and used it to make a stress test for interactive performance. In our testing the maximum time to render a frame including pause time is reduced from 272ms to 50ms.
The new GC in Chrome improves interactive performance and opens up new possibilities for the interactive web. If you are developing highly interactive web apps or games, please try it out and share your experiences. It is available now on the dev channel.
11 comments:
▴triune. said...
OSX 10.7.2
Chrome Stable:
8000/320 13(max = 293) ms 3050 frames
Score 2
0-10ms => 23
10-20ms => 2563
20-30ms => 243
30-40ms => 78
40-50ms => 105
50-60ms => 2
60-70ms => 1
70-80ms => 1
80-90ms => 1
110-120ms => 1
150-160ms => 16
160-170ms => 1
280-290ms => 7
290-300ms => 8
Chrome Canary
8000/320 17(max = 129) ms 3232 frames
Score 24
0-10ms => 4
10-20ms => 2942
20-30ms => 123
30-40ms => 12
40-50ms => 143
70-80ms => 1
90-100ms => 3
100-110ms => 1
110-120ms => 1
120-130ms => 2
November 21, 2011 12:12 PM
Tom Felker said...
I'd like to see some work done on scrolling performance. When using Google Reader, it often takes hundreds of milliseconds to redraw, even on very fast computers. Improve the worst things first.
November 21, 2011 12:54 PM
Pavel said...
Block Google+ button and performance gets much better. http://www.howtogeek.com/98137/fix-google-reader-lag-by-blocking-google-plus-button/
Though scrolling does need more work...i.e smooth scroll GPU offloading?
November 21, 2011 6:37 PM
▴triune. said...
Firefox 10.0a2
8000/320 16(max = 104) ms 3642 frames
Score 51
0-10ms => 1
10-20ms => 3617
20-30ms => 8
30-40ms => 1
40-50ms => 1
80-90ms => 10
100-110ms => 4
November 22, 2011 7:48 AM
streetwolf said...
Firefox/11.0a1
8000/320 17(max = 75) ms 3575 frames
Score 127
0-10ms => 38
10-20ms => 3515
20-30ms => 7
30-40ms => 1
40-50ms => 3
50-60ms => 1
60-70ms => 5
70-80ms => 5
November 22, 2011 6:54 PM
Thomas M Grasso, Esq. said...
My Google Chrome browser has decided to no longer work. It is certainly nothing I have done, and I see by various blogs and development sites that it is Google's problem not mine. The problem is rampant and persistent. We lay people who are running businesses, like me, have not time nor energy to sift through page after page of attempted solutions. The easy fix for me is to uninstall Chrome outright and use Firefox exclusively, which I'm going to do after I post this. When you folks figure out how to make your program work, how about sending an email to all account holders and giving us a one button solution. The general public has better things to do that debug your now half-assed, totally unresponsive program. What use is your game changing performance thing when Chrome does not even load? Look after the important things first rather than tinker to find a few milliseconds here and there.
Regards,
Extremely Displeased Chrome User
November 23, 2011 6:29 AM
YaroslavKa said...
Chromium 17.0.950.0 (Asus F3Sc, Win 64bit)
0-10ms => 1
10-20ms => 251
20-30ms => 190
30-40ms => 496
40-50ms => 417
50-60ms => 119
60-70ms => 67
70-80ms => 37
80-90ms => 11
90-100ms => 30
100-110ms => 12
110-120ms => 4
120-130ms => 1
130-140ms => 1
140-150ms => 2
160-170ms => 1
180-190ms => 1
370-380ms => 1
November 24, 2011 5:02 AM
Jor said...
@Thomas M Grasso, Esq.
If you're using the Dev release, which this blog entry is about, then you have no excuse as to why the browser doesn't work for you. You want the Stable release instead.
November 24, 2011 9:38 AM
Unknown said...
--- Firefox 8.0.1 ---
8000/320 16(max = 64) ms 3817 frames
Score 238
0-10ms => 5
10-20ms => 3784
20-30ms => 2
30-40ms => 13
50-60ms => 12
60-70ms => 1
--- Chrome 17.0.942.0 ---
8000/320 16(max = 109) ms 3545 frames
Score 42
0-10ms => 10
10-20ms => 3346
20-30ms => 11
30-40ms => 160
40-50ms => 6
50-60ms => 3
70-80ms => 4
90-100ms => 3
100-110ms => 2
November 24, 2011 11:35 AM
NT Man said...
November 25, 2011 6:28 AM
NT Man said...
November 25, 2011 6:34 AM
Post a Comment