Macworld Forums

Macworld Forums: Opera 12: A work in progress finally shows real improvements - Macworld Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Opera 12: A work in progress finally shows real improvements

#1 User is offline   Macworld 

  • Story Poster
  • Group: MW Bot
  • Posts: 31,702
  • Joined: 30-November 07

Posted 06 July 2012 - 03:31 AM

Post your comments for Opera 12: A work in progress finally shows real improvements here
0

#2 User is offline   reformedgeek 

  • Newbie
  • Pip
  • Group: New Members
  • Posts: 1
  • Joined: 06-July 12

  Posted 06 July 2012 - 04:14 AM

"This free, open-source browser’s designers"? Last I checked, Opera was closed-source
0

#3 User is offline   faithinformed 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 7
  • Joined: 10-August 09

  Posted 06 July 2012 - 04:18 AM

FYI, in the second paragraph below the comparison chart you use 'Chrome' a few times instead of 'Opera'. Still, great overview, thanks for the info.
0

#4 User is offline   davidlfoster 

  • Member
  • PipPip
  • Group: Members
  • Posts: 109
  • Joined: 13-May 08

  Posted 06 July 2012 - 04:44 AM

You can set Chrome as your default browser, or any iOS browser for that matter.

Look up Cydia.
0

#5 User is offline   bager 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 11
  • Joined: 24-June 05

  Posted 06 July 2012 - 06:24 AM

If you add Google's V8 benchmark and very extensive Dromaeo JavaScript benchmark to your browser tests, test results would better reflect real world usage.
Each of JavaScript benchmark has it's own strengths, but I believe SunSpider benchmark is pretty much outdated for modern JavaScript JIT driven runtimes.

You may also consider to test browsers with Peacekeeper (http://peacekeeper.futuremark.com/). It consists of a bunch of browser performance tests.
0

#6 User is offline   makpe 

  • Member
  • PipPip
  • Group: Members
  • Posts: 21
  • Joined: 26-February 10

Posted 06 July 2012 - 11:14 AM

 bager, on 06 July 2012 - 06:24 AM, said:

If you add Google's V8 benchmark and very extensive Dromaeo JavaScript benchmark to your browser tests, test results would better reflect real world usage.

I'm puzzled as to why you think wholly artificial benchmarks in any way represent real world usage. Particularly when the V8 benchmark was created specifically to run well in Chrome (it was designed with Chrome's architecture in mind).
0

#7 User is offline   bonesb 

  • Member
  • PipPip
  • Group: Members
  • Posts: 516
  • Joined: 12-September 01

Posted 06 July 2012 - 02:38 PM

 reformedgeek, on 06 July 2012 - 04:14 AM, said:

"This free, open-source browser’s designers"? Last I checked, Opera was closed-source

You're spot-on - Opera isn't open-source. Opera does run on several open-source OSes - the author's point is in error.
0

#8 User is offline   bager 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 11
  • Joined: 24-June 05

Posted 08 July 2012 - 07:53 AM

 makpe, on 06 July 2012 - 11:14 AM, said:

 bager, on 06 July 2012 - 06:24 AM, said:

If you add Google's V8 benchmark and very extensive Dromaeo JavaScript benchmark to your browser tests, test results would better reflect real world usage.

I'm puzzled as to why you think wholly artificial benchmarks in any way represent real world usage. Particularly when the V8 benchmark was created specifically to run well in Chrome (it was designed with Chrome's architecture in mind).

Benchmarking is a very difficult subject indeed. I do not believe there is a single benchmark representing all points of view, therefore I suggest MacWorld runs as many as possible, SunSpider, Dromaeo, Kraken, Peacemark, ... as each of them has their own strengths. SunSpider tests are so short living that a modern Javascript JIT compilers have trouble detecting and optimizing hot-spots. V8 tests last longer so JIT can optimize hot-spots. V8 tests are more representative of long running applications (e.g. webmail).

P.S: V8 benchmark was not create to run well in Chrome. It was created to improve Chrome JIT compiler.
0

#9 User is offline   Scott76 

  • Member
  • PipPip
  • Group: Members
  • Posts: 30
  • Joined: 12-December 07

  Posted 09 July 2012 - 05:13 AM

Interesting... Opera only scored 385 +9 bonus points on my system, a 27-inch iMac running Snow Leopard. It was still higher than Safari and Firefox but below Chrome.

I wonder how much of HTML 5 is system dependent? Or is there something different in the implementation of these browsers on each platform?
0

#10 User is offline   makpe 

  • Member
  • PipPip
  • Group: Members
  • Posts: 21
  • Joined: 26-February 10

Posted 20 July 2012 - 04:11 PM

 bager, on 08 July 2012 - 07:53 AM, said:

 makpe, on 06 July 2012 - 11:14 AM, said:

 bager, on 06 July 2012 - 06:24 AM, said:

If you add Google's V8 benchmark and very extensive Dromaeo JavaScript benchmark to your browser tests, test results would better reflect real world usage.

I'm puzzled as to why you think wholly artificial benchmarks in any way represent real world usage. Particularly when the V8 benchmark was created specifically to run well in Chrome (it was designed with Chrome's architecture in mind).

Benchmarking is a very difficult subject indeed. I do not believe there is a single benchmark representing all points of view, therefore I suggest MacWorld runs as many as possible, SunSpider, Dromaeo, Kraken, Peacemark, ... as each of them has their own strengths. SunSpider tests are so short living that a modern Javascript JIT compilers have trouble detecting and optimizing hot-spots. V8 tests last longer so JIT can optimize hot-spots. V8 tests are more representative of long running applications (e.g. webmail).

P.S: V8 benchmark was not create to run well in Chrome. It was created to improve Chrome JIT compiler.


The point is that these artificial benchmarks are still artificial, and the V8 benchmark in particular is useless because it was designed with Chrome (V8) in mind. It's supposed to show off V8 and is optimized specifically for the way V8 does things (and leaves out things it's extremely slow at!), so other JS engines will always be at a disadvantage.
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users