This article will take a look at how MeeGo develops and destroys Android2.2 in Javascript testing. I believe you will have a new understanding of the concept of Meego development through a simple introduction in this article. For details, see this article.
In Javascript testing, MeeGo development destroys Android2.2
Note: the title of this article refers to a recent ARSTechnica article, and cannot be taken seriously. Let's take a look at the following reports to learn more about the situation. In fact, this is all about the browser engine and platform, rather than the operating system.
Today, I started a series of tests on the Aava prototype phone. The first one I want to perform is a Sunspiderjavascript test. It is a central processor-intensive and is an important part of the chain event that allows WEB programs to display on your browser. Yes, it is one of multiple variables and an important indicator of CPU performance.
I 've been recording SunSpider tests and you can also add the list you want to test), and I'm impressed with the improvements in software and hardware. In the ARM-based world, the best devices of the same kind produce SunSpider results (iPad, iPhone 4) within 10 seconds ), some new devices have been completed in less than 6 seconds. For more information, see references ). In Intel's world, netbooks use the latest Chromebuild to generate Sunspider results in about 2 seconds ).
The above is the result of my current Aava call. 4215 ms. It runs 1.5 Ghz in Intel's Moorestown) and uses the same CPU as the netbook. On the netbook, run Sunspider on the latest Firefoxbuild or FirefoxMobilebuild on the Aava phone developed based on Meego. The difference is very small. For a prototype phone, 4.2 seconds is impressive. These numbers confirm the CPU speed again and specify that the sunspider speed will be reduced to 2 seconds to use the latest Chrome or Androidbrowserbuild ). Try Sunspider on your phone or PC browser to see how many points you can get. For your reference, I use UMPC as my trusted PC. It runs 1.6 GhzAtomCPU and returns 4.1 seconds. The real speed of a desktop PC is no less than 0.5 seconds.
We are talking about the power of PC here, but there are two points that we must remember. 1) multi-core ARM-based devices are coming soon. Dual-core, 1.2GhzSnapdragon platform is likely to reach 2 ~ The speed range of 3 seconds. 2) We must also remember that if you want to continue running this test on these high-energy platforms, you will experience crashes within several hours.