Google Chrome Canary hits v10, Crankshaft turbocharges V8 JavaScript engine

Crankshaft is made up of four components:
- a runtime profiler for identifying code that uses a significant number of CPU cycles
- a base compiler for generating code more quickly
- an optimizing compiler which re-compiles code pinpointed by the profiler
- deoptimization mechanism that allows Crankshaft to recover from overly-optimistic code optimizations
...And for those of you wondering when Chrome was going to hit version ten, you've got your answer. It's already happened to the Canary build -- so hit your wrench menu > About Google Chrome and restart to update yourself to Chrome X! There's not much new that you'll notice right off the bat, with the exception of a selectable Instant option and experimental geolocation features in about:flags.












Comments
9
Subscribe to commentsGanoes ParanDec 7th 2010 11:13PM
annnd Chromium also hit version X lol
war59312Dec 8th 2010 1:23AM
About time, we get double digits. ;)
What a joke, should be 0.3 or so really.
KualaBeeDec 8th 2010 2:11AM
I wish Firefox had this pace of development. When Firefox 4.0 was announced it goal was "javascript performance near or even with Chrome 5..." and it still uses Chrome 5 in it's official comparison in their meeting notes. Now Chrome is at 10 and javascript performance gap between Chrome 5 and 10 is pretty wide. When delayed and delayed Firefox 4.0 comes out, it might be already outdated or will be in immediate future by Chrome.
FDer99Dec 8th 2010 7:31AM
@KualaBee
Sorry but you have no idea what you're talking about
http://arewefastyet.com/
MySchizoBuddyDec 8th 2010 6:23AM
@FDer99 the link you posted doesn't mention the chrome version at all. SO how do you know they are using the latest chrome build for their comparisons.
MySchizoBuddyDec 8th 2010 6:24AM
@FDer99 the link you posted doesn't mention the chrome version. so how do you know they are using the latest chrome version
KualaBeeDec 8th 2010 7:09AM
@FDer99 Actually I do, from the horse's mouth.
https://wiki.mozilla.org/Platform/2010-11-30
"Platform (there is a team-by-team goals breakdown, as well)
[DONE] Javascript performance near or even with Chrome 5 on their benchmarks (within 20% on SS, 30% on V8), with substantial wins on our benchmarks. (Windows, in-browser.) "
ab1Dec 8th 2010 10:39AM
Did I miss something? I thought the general consensus was that with Javascript being so fast, and everyone within a few milliseconds of everyone else, that most of the benchmarks had become useless, and consequently focusing on javascript speed was a bit pointless. Or just for that benchmark? I ask because the point of a benchmark is to give some real life comparison, not to have some runaway speed on some pointless statistic. Any hit on CPU/RAM for this speed increase. I know most people on here probably have superb machines, but if someone is running a pentium 3.0 CPU with 512MB RAM, is Chrome going to want to half your memory..lol
Or was that over something else?
http://downloadsquad.switched.com/2010/10/30/fireffox-4-max-sunspider-javascript-benchmark/
And am I the only one worried that the better the browsers become at rendering Javacscript, the more likely thousands of websites will start putting in pointless annoying mini apps in their webpages.
For instance, the browser bar at any of the cnet pages, the share bar that appears on quite a few pages and so forth. (I am not sure if they are Javascript, but they are totally annoying and irritating).
Bleargh....every advancement in browser speed, seems to be an invitation to website to fill up their pages with pointless annoyances to slow you down again.
HarshDec 8th 2010 12:18PM
@KualaBee
That milestone was reached several weeks ago. Development hasn't stopped since then, they're still competitive against the latest chrome dev builds.
@MySchizoBuddy
AWFY compares the latest v8 engine development tip against the latest Spidermonkey tip. Meaning newer than even the latest canary build. Unfortunately the site hasn't been updated in a while and doesn't reflect the performance improvements made by the new crankshaft compiler. My understanding is that the site is being refactored to show more benchmarks on more OSes.