![]() With all this in mind, taking an average of the two measures, we again stick with Firefox for its economical use of resources in both scenarios. But when the browser is closed the remnants that stay in memory are practically null – exactly the opposite of what happens with Chrome, for example, which leaves a whopping 123MB inflated in your device memory. When you open it the app opens different processes for each tab, making the total RAM use considerable, though with an enormous boost to stability, as if one tab crashes it won’t bring the whole app down. The case of Opera is particularly interesting. ![]() We’ve contrasted the amount of RAM taken up when the browser is both open and closed to see which elements it leaves running. Winner: Odd and revealing results this time around with a deeper analysis than we’ve done on previous occasions. Mozilla Firefox: 32MB in memory | 203MB when running.Plus to contrast that info we use the useful app Simple System Monitor which lets us keep a monitor window open in real time while we open the aforementioned browser tabs. More specifically, we opened the browser with three tabs immediately after a clean startup of the device: the Uptodown homepage, Wikipedia, and a blank Google search tab. We’ve taken our data here straight from Android’s own app manager and included all open elements for each one. RAM consumptionĭon’t be fooled: the amount of space occupied by an app is not the same as the memory used by the associated running processes and the cache generated for the optimum functioning of the app in question. Unlike our analysis from last September, we’ve run our tests this time after closing the services run by Chrome in the background so that we’re measuring everything by the same metric and getting rid of the “home advantage” Chrome enjoyed due to so many of its functions being resident in the system. Winner: In this case, Firefox was the fastest responder from a cold start. This time we’ve opted to do 25 opening cycles to get a measure that’s as close as possible to the normal situation where the content being accessed is already resident in the browser memory. To measure this indicator we’ve used the free Android app DiscoMark, which gauges how long it takes a set of apps to open by taking the average time from several iterations. Opening timeĪnother important thing to keep in mind is how long it takes a browser to open. Interesting tidbit: Opera Browser doesn’t break 2MB in terms of temporary data storage. Winner: Except for Chrome, all the apps have lightly inflated the amount of space they take up since last year, though even with this increase Firefox remains the lightest one. Mozilla Firefox: 53.04 + 24MB of data (32.23MB in the APK).Google Chrome: 78.76MB App + 23MB of data (44.83MB in the APK).We’re going to consider the size of the APK before a clean installation and the app itself afterward, plus the amount of data used after doing all the tests below. How much space an app takes up is a super important thing to keep in mind given how limited so many devices are in this respect. The intrinsic capabilities of each app fall beyond the scope of this analysis, as this sort of data can be easily consulted on each developer’s website. 114522, and UC Browser 11.2.5.932. We’ll be looking at: how much memory the app takes up after its installation, opening time after successive iterations, RAM consumed when running, performance based on several benchmarks, and an admittedly subjective but still important evaluation of usability. In the interest of contrasting today’s analysis with our previous ones, we’re going to be using the same test device as we used a year ago – a Google Nexus 7 (2013) with Android 6.0.1 – while the versions for each browser are the latest ones to date released on the stable channel: Google Chrome. It’s now been a full six months since our last browser comparison (from September 2016), so you’re probably eagerly awaiting our latest half-yearly report on the four most popular Android browsers at the moment: Google Chrome, Mozilla Firefox, UC Browser, and Opera. As on previous occasions our comparison covers several aspects: RAM use, app opening speed, and compatibility.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |