After having reported the number of applications not currently compatible with a thorough analysis of performance and functionality, we return to talk about today's Lumia 610 and its compartment hardware. Thanks to an article by András Velvárt, Silverlight MVP and developer of 3D Browser Surfcube, we have examined the performance of CPU, GPU and Memory of the Nokia Lumia 610.
The new entry level Nokia with 800Mhz processor and 256Mb of Ram, was subjected to comparisons with Lumia 800 with 1.4GHz processor and 512Mb of Ram, and LG Optimus 7 with 1 GHz processor and 512Mb of Ram.
As for the tests on the processor the developer decided to compare the timing of starting the application drawing of the stars of Lumia 610, LG Optimus 7, and Lumia 800 SDK emulator.
The report of this application have shown that with the increase of the elements to load the processor Lumia 610 has often approached the start-up time required by the LG's Optimus 7, ensuring all in all a good computing power.
The real surprise comes from the GPU performance. As can be seen in the table above, the Lumia 610 is able to obtain a good number of FramesPerSecond, quite easily surpassing the performance offered by the Windows Phone by LG!
The FPS in fact begin to fall on an Optimus 7 Fill Rate (parameter used to evaluate the performance of a video card) of only 2.5, revealed a critical point at 5. The Lumia 610 shows much more stable and efficient, arriving at the threshold of 30FPS with a Fill Rate to 8.5.
So, ignoring the fact that some applications are still running pretty slow, the real problem of Lumia 610 seems to be the volatile memory: the 90MB reserved for each application with the devices with 512Mb RAM, 60Mb of Lumia down to 610 . Fortunately, Microsoft Windows Phone Tango has worked extensively on Paging File, providing additional virtual memory for applications, but this technique can cause swapping On the same time because of delays to the system is increased the workload of the processor.
- Paging File : To the memory of the physical RAM is the amount of virtual memory paging file, which is a file that the operating system created to simulate a larger amount of RAM.
Perhaps with further improvement of Frameworks SDK and things will greatly improve, but for now we can not help that the question asked yesterday would not have been better to choose 384MB of RAM?
