Slashdot Mirror
Firefox vs Chrome: Speed and Memory (laptopmag.com)
Mashable aleady reported Firefox Quantum performs better than Chrome on web applications (based on BrowserBench's JetStream tests), but that Chrome performed better on other benchmarks. Now Laptop Mag has run more tests, agreeing that Firefox performs beter on JetStream tests -- and on WebXPRT's six HTML5- and JavaScript-based workload tests.
Firefox Quantum was the winner here, with a score of 491 (from an average of five runs, with the highest and lowest results tossed out) to Chrome's 460 -- but that wasn't quite the whole story. Whereas Firefox performed noticeably better on the Organize Album and Explore DNA Sequencing workloads, Chrome proved more adept at Photo Enhancement and Local Notes, demonstrating that the two browsers have different strengths...
You might think that Octane 2.0, which started out as a Google Developers project, would favor Chrome -- and you'd be (slightly) right. This JavaScript benchmark runs 21 individual tests (over such functions as core language features, bit and math operations, strings and arrays, and more) and combines the results into a single score. Chrome's was 35,622 to Firefox's 35,148 -- a win, if only a minuscule one.
In a series RAM-usage tests, Chrome's average score showed it used "marginally" less memory, though the average can be misleading. "In two of our three tests, Firefox did finish leaner, but in no case did it live up to Mozilla's claim that Quantum consumes 'roughly 30 percent less RAM than Chrome,'" reports Laptop Mag.
Both browsers launched within 0.302 seconds, and the article concludes that "no matter which browser you choose, you're getting one that's decently fast and capable when both handle all of the content you're likely to encounter during your regular surfing sessions."
You might think that Octane 2.0, which started out as a Google Developers project, would favor Chrome -- and you'd be (slightly) right. This JavaScript benchmark runs 21 individual tests (over such functions as core language features, bit and math operations, strings and arrays, and more) and combines the results into a single score. Chrome's was 35,622 to Firefox's 35,148 -- a win, if only a minuscule one.
In a series RAM-usage tests, Chrome's average score showed it used "marginally" less memory, though the average can be misleading. "In two of our three tests, Firefox did finish leaner, but in no case did it live up to Mozilla's claim that Quantum consumes 'roughly 30 percent less RAM than Chrome,'" reports Laptop Mag.
Both browsers launched within 0.302 seconds, and the article concludes that "no matter which browser you choose, you're getting one that's decently fast and capable when both handle all of the content you're likely to encounter during your regular surfing sessions."
When will Noscript 10 be available for Firefox? Until that's released, Firefox is garbage. If developer builds allow legacy extensions to run , the Firefox developers were more than capable of doing so in official releases. Quite simply, the goal is to prevent users from running legacy extensions. In the process, security and functionality have been reduced for everyone.
download statusbar, classic theme restorer, noscript. Without all the addons that made Firefox 3.0 great, speed is useless. Like a car without seats, or a bar without beer.
It is like IE around 2000. It does stuff behind your back. So, we can see it but you can't unless you look at it from a perspective outside the walled garden.
Everything I write is lies, read between the lines.
Tell us which one is faster to remove all the ads, shutting up all the audio and video, blocking facebook , pinterest and twitter buttons, preventing fingerprinting and trackers, blocking webRTC and all 30 external javascript links that each page seems to 'need' these days and ... then we can talk.
These Mozilla/Firefox submissions are very important and relevant. It's critical for us to let people know the truth about FF 57. It's being portrayed as a great release, but in my experience with it it's the opposite; it's terrible, I think. If it weren't for these submissions, it would be a lot easier for innocent victims to be mislead about FF 57. At least people might learn about their broken extensions before upgrading. And these submissions are a great place to let Firefox victims know about alternatives like Brave, Chrome and Vivaldi.
Which of those benchmarks measures browser performance after leaving a couple dozen tabs open for three weeks? Huh?
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
It only choked on the pdf from this article where cpu went nuts
So the real problem is using a browser to render PDFs. We're using browsers to do half-assed duplicate work while proper tools for the job already exist.
Escher was the first MC and Giger invented the HR department.