Actual JavaScript Engine Performance

It would be even more interested to see performance based on the javascript that, say, twitter and facebook use, but I would guess that it's very difficult to feed the scripts the correct sort of data for benchmarking.

Re: Actual JavaScript Engine Performance

#6

Post by ktsmith » Thu, Apr 21, 2011, 5:05 PM UTC

phren0logy wrote: post #2

Wow, IE10 has some legs. I'm shocked to see how Chrome performance compares. If Chrome is on the slower side, I think the real winner is everyone who uses the web, because that means all of these modern browsers are FAST.

Comparing IE10 to Chrome 10 isn't exactly apples to apples. Chrome 11 or 12 should be compared to IE10 since those are the development versions.

Re: Actual JavaScript Engine Performance

#7

Post by kenjackson » Thu, Apr 21, 2011, 5:12 PM UTC

ktsmith wrote: post #6

phren0logy wrote: post #2

Wow, IE10 has some legs. I'm shocked to see how Chrome performance compares. If Chrome is on the slower side, I think the real winner is everyone who uses the web, because that means all of these modern browsers are FAST.

Comparing IE10 to Chrome 10 isn't exactly apples to apples. Chrome 11 or 12 should be compared to IE10 since those are the development versions.

Could you provide links to recommended builds? If Crockford is reading maybe he can add them.

Re: Actual JavaScript Engine Performance

#8

Post by kenjackson » Thu, Apr 21, 2011, 5:14 PM UTC

TheBoff wrote: post #5

This is really fascinating, although a blow for the chrome team. It would be even more interested to see performance based on the javascript that, say, twitter and facebook use, but I would guess that it's very difficult to feed the scripts the correct sort of data for benchmarking.

This is not a blow to the Chrome team. Chrome came out to raise the water level and lift all boats. They're achieving that. Sure, a nice bonus is to be the fastest at all times, but leapfrogging is probably even better as it keeps everyone heads down rather than just conceeding to Chrome.

Re: Actual JavaScript Engine Performance

#9

Post by eekfuh » Thu, Apr 21, 2011, 5:16 PM UTC

Now who is going to mix this with DOM manipulation, so we can actually see how the end-user is effected.

If the JS engine is crazy fast and the DOM renderer blows, it won't make a bit of difference, unless it's purpose is as a server technology.

Re: Actual JavaScript Engine Performance

#10

Post by ktsmith » Thu, Apr 21, 2011, 5:18 PM UTC

kenjackson wrote: post #7

ktsmith wrote: post #6

Earlier quoted context omitted.

Comparing IE10 to Chrome 10 isn't exactly apples to apples. Chrome 11 or 12 should be compared to IE10 since those are the development versions.

Could you provide links to recommended builds? If Crockford is reading maybe he can add them.

You can get installers for whatever the latest build is in each channel here: http://dev.chromium.org/getting-involved/dev-channel

It's updated so frequently I'm not sure there's a better way to get a specific build.