That's to be expected but something one should consider especially on devices where RAM is scarce.īenchmarks on the other hand show only marginal differences which means that users won't see a performance boost in either version when compared to the other.
RAM usage is nearly the same on start but once all ten websites were fully loaded it was apparent that the 64-bit version of Firefox used way more RAM than the 32-bit version. In addition, it did not freeze while running the RoboHornet benchmark while Google Chrome did. Every other browser experienced at least one freeze while running the benchmarks.Īnother interesting observation is that Vivaldi outperforms Google Chrome in some benchmarks and with RAM usage even though it is still a beta release. The only two browsers that ran all tests without freezes or hangs were Mozilla Firefox and Microsoft Edge. Google Chrome did not complete the RoboHornet and Dromaeo benchmarks, Pale Moon froze while running the JetStream benchmark, and Vivaldi froze running the Dromaeo benchmark. One surprising result of the tests that I ran was that hangs were experienced quite frequently. The benchmarks test the browser's JavaScript performance. While RAM usage is not that much of an issue anymore on modern systems that come equipped with 4 Gigabyte of RAM or more, it needs to be considered that the browser is just one of the programs run on a system and that a high RAM usage may result in performance drops if other demanding applications are run. The first two tests highlight the browser's RAM usage.
0 kommentar(er)
