Opera Mobile 10.1 Symbian Beta 2 - Much Improved JavaScript Performance

Opera Mobile 10.1 Beta 1 Sunspider Benchmark Opera Mobile 10.1 Beta2 Sunspider Results

Today Opera Software released a new Beta of Opera Mobile 10.1 for Symbian^1, Symbian^3 and Symbian 3rd Edition phones. Download Beta 2 at m.opera.com/next.  The main feature of the new release is the addition of the Carakan JavaScript engine's Just In Time (JIT) compiler. Opera claims the new compiler makes JavaScript execution up to four times faster.

I tested that claim by running the popular Sunspider JavaScript benchmark on a Nokia N95-3, first with Opera Mini 10.1 Beta 1 and then with the new Beta. I think Opera is being too modest. Opera 10.1 Beta 2 was over 7 times faster on Sunspider than Beta 1; 24,516.8 ms vs 181,405.8 ms. Here are links to detailed results on the Sunspider benchmark tests for Beta 1 and Beta 2

I also tried Google's V8, another JavaScript benchmark.  Both Beta 1 and Beta 2 ran out of memory running the last test of the V8 suite. Google says that test, called Splay, "...exercises the automatic memory management subsystem".  Higher memory usage is a known issue with both Betas so presumably that is something Opera is working on.  On the six V8 test components that the Opera Browsers did complete, Beta 2 again did much better scoring 289.5 vs. 33.8 or 8.5 times better!

The table below summarizes the two Betas performance and their memory footprint after each test.  Memory was measured with Phonetinfo 1.2 and is the difference in free RAM before starting Opera and after each test.

Test Beta 1 Beta 2 Beta 1 Memory Beta2 Memory
Sunspider 181,405.8 ms 24,516.8 ms 18,168 KB 27,248 KB
V8 33.8 289.5 0 (DNF) 0 (DNF)

In real world tests visiting pages that use Javascript extensively, Beta 2's performance improvement was noticeable However don't expect to see a huge difference with most pages.

  • The Touch version of Google Reader, which is a little sluggish on the N95 with Beta 1 is downright snappy with Beta 2. The experience with Beta 2 is every bit as good as  on my Android phone.
  • The PC version of Reader, which i find unusable in Beta 1, is better with Beta 2,but still not something I would use willingly. The delay opening feeds and scrolling through items is now tolerable rather than unbearable.  However items still aren't automatically marked as read when scrolling past them.
  • I did not see any noticeable difference between Beta 1 and 2 with the Touch version of Buzz, which is reasonably responsive in both Betas.

I was very happy to see that my bookmarks and speed dials were preserved when installing Beta 2 over Beta 1, something previous versions of Opera Mobile did not do.  Unfortunately saved passwords are not retained when upgrading.

Make no mistake, this is a Beta version. Opera lists the following known issues in the 10.1 Beta 2:

  • Higher memory usage for Carakan with JIT compilation.
  • Due to timing issues with different geolocation information providers (WiFi, cell towers, GPS) first request may have poor precision
  • Fast scrolling on Touch devices not optimized for page rendering
  • Opera Link may not work when using APN with a proxy configured
  • Some SVGT images may appear to freeze on Nokia E-series phones
  • If SIM card is not registered, or phone is in flight mode, first geolocation request in a browser session may fail

Other than the out of memory errors running the V8 benchmark, I didn't experience any  issues with this Beta. However, there are two reports of problems on E-series devices on the Opera Mobile for Symbian forum.  If it does turn out to unstable for you, here are links to download and reinstall Beta 1 and the Opera 10 stable version.

2 thoughts on “Opera Mobile 10.1 Symbian Beta 2 - Much Improved JavaScript Performance

    • Thanks Rodakk, Comparing the nunbers you got on the six tests that I could run, yours are all 2 to 3 times better. The N95-3 is not a slugish phone, but the E5 seems is clearly much quicker. Nice to see in a relatively low end smartphone.

Leave a Reply

Your email address will not be published. Required fields are marked *