4 ms·

Can anyone explain this? http://tctechcrunch2011.files.wordpress.com/2013/06/scaled-screen-shot-2013-06-10-at-1-35-27-pm.png?w=620&h=473 http://tctechcrunch2011

by rfnslyr 13y ago

Can anyone explain this? http://tctechcrunch2011.files.wordpress.com/2013/06/scaled-screen-shot-2013-06-10-at-1-35-27-pm.png?w=620&h=473 http://tctechcrunch2011.files.wordpress.com/2013/06/scaled-s... Is that real or just BS?

mosqutip 13y ago
Seems BS to me. Looks just like their "performance" pages for the Macbook Pro on the Apple website.
- rfnslyr 13y ago
  Yeah I'm going to need a technical rundown before I believe some random slide.
conroy 13y ago
I'm going with BS until they provide more details. They don't even mention what version of Chrome and Firefox they are testing against.
othermaciej 13y ago
Its's real. You can try the benchmark yourself here, and learn how it is different from other JS benchmarks <http://jsbench.cs.purdue.edu/> http://jsbench.cs.purdue.edu/>.
mdasen 13y ago
It's likely "real". By real, I mean that I just ran JSBench on my MacBook Air with Safari and Chrome (latest released version of each) and Safari came out significantly ahead (Chrome took 1.75x longer). They're claiming 2.53x faster than Chrome in that slide so that would mean an improvement of probably around 50% over the current Safari in terms of JS speed on this benchmark. So, it would seem that this particular benchmark already favors Safari's JS engine and that the next Safari will improve on the current Safari's performance. Now, the issue with JSBench is that it's real-world JS, but only from 5 sources. Granted, they're 5 sources that are very high-trafficked, but it's still a small sample size (http://jsbench.cs.purdue.edu/ http://jsbench.cs.purdue.edu/). Similarly, Apple showed off SunSpider benchmarks showing the next Safari being faster than Chrome. The current Safari on my MacBook Air beats Chrome, with Chrome taking 6.9% longer. So, part of it is that each browser maker has its preferred benchmarks.
- othermaciej 13y ago
  Other JS benchmarks are not based on highly-trafficked real-world sources at all, so perhaps "real" is relative.
- will_work4tears 13y ago
  What would it say if you ran a benchmark with Safari on your Macbook and Chrome on your Windows/*nix box and Chrome came out significantly ahead?
  - eridius 13y ago
    Benchmarks taken with different software on different hardware isn't very useful.
shinratdr 13y ago
Why would it BS? This is almost always the case. Safari has plenty of notches on it's belt, it's just that the Chrome and FF teams do far tighter release cycles allowing for improvements like this to be pushed out the door faster. Safari is a great browser, always has been. This is hardly surprising or new, just like it's not novel that Chrome will meet and exceed those stats within a month or two of the release of Safari 7.
- othermaciej 13y ago
  I expect other browsers could greatly improve JSBench performance if they focused on it. But I would be quite surprised if they matched Safari's current results in a month. It took a lot more than a month and significant architectural work to get those results in the first place.

by rfnslyr 13y ago

mosqutip 13y ago

Seems BS to me. Looks just like their "performance" pages for the Macbook Pro on the Apple website.

rfnslyr 13y ago
Yeah I'm going to need a technical rundown before I believe some random slide.

conroy 13y ago

I'm going with BS until they provide more details. They don't even mention what version of Chrome and Firefox they are testing against.

othermaciej 13y ago

Its's real. You can try the benchmark yourself here, and learn how it is different from other JS benchmarks <http://jsbench.cs.purdue.edu/> http://jsbench.cs.purdue.edu/>.

mdasen 13y ago

It's likely "real". By real, I mean that I just ran JSBench on my MacBook Air with Safari and Chrome (latest released version of each) and Safari came out significantly ahead (Chrome took 1.75x longer). They're claiming 2.53x faster than Chrome in that slide so that would mean an improvement of probably around 50% over the current Safari in terms of JS speed on this benchmark. So, it would seem that this particular benchmark already favors Safari's JS engine and that the next Safari will improve on the current Safari's performance. Now, the issue with JSBench is that it's real-world JS, but only from 5 sources. Granted, they're 5 sources that are very high-trafficked, but it's still a small sample size (http://jsbench.cs.purdue.edu/ http://jsbench.cs.purdue.edu/). Similarly, Apple showed off SunSpider benchmarks showing the next Safari being faster than Chrome. The current Safari on my MacBook Air beats Chrome, with Chrome taking 6.9% longer. So, part of it is that each browser maker has its preferred benchmarks.

othermaciej 13y ago
Other JS benchmarks are not based on highly-trafficked real-world sources at all, so perhaps "real" is relative.
will_work4tears 13y ago
What would it say if you ran a benchmark with Safari on your Macbook and Chrome on your Windows/*nix box and Chrome came out significantly ahead?
- eridius 13y ago
  Benchmarks taken with different software on different hardware isn't very useful.

shinratdr 13y ago

Why would it BS? This is almost always the case. Safari has plenty of notches on it's belt, it's just that the Chrome and FF teams do far tighter release cycles allowing for improvements like this to be pushed out the door faster. Safari is a great browser, always has been. This is hardly surprising or new, just like it's not novel that Chrome will meet and exceed those stats within a month or two of the release of Safari 7.

othermaciej 13y ago
I expect other browsers could greatly improve JSBench performance if they focused on it. But I would be quite surprised if they matched Safari's current results in a month. It took a lot more than a month and significant architectural work to get those results in the first place.