Browser speed test

From HandWiki
Revision as of 18:07, 8 February 2024 by MedAI (talk | contribs) (add)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Short description: Type of computer benchmark

A browser speed test is a computer benchmark that scores the performance of a web browser, by measuring the browser's efficiency in completing a predefined list of tasks. In general the testing software is available online, located on a website, where different algorithms are loaded and performed in the browser client. Typical test tasks are rendering and animation, DOM transformations, string operations, mathematical calculations, sorting algorithms, graphic performance tests and memory instructions. Browser speed tests have been used during browser wars to prove superiority of specific web browsers. The popular Acid3 test is no particular speed test but checks browser conformity to web standards (though it checks whether a general performance goal is met).

General tests

Speedometer 2.0

Speedometer was originally developed by the WebKit team at Apple and released in 2014 and was updated in 2018.[1] Speedometer 2.0 tests a browser's Web app responsiveness by timing simulated user interactions.

This benchmark simulates user actions for adding, completing, and removing to-do items using multiple examples in TodoMVC. Each example in TodoMVC implements the same todo application using DOM APIs in different ways. Some call DOM APIs directly from ECMAScript 5 (ES5), ECMASCript 2015 (ES6), ES6 transpiled to ES5, and Elm transpiled to ES5. Others use one of eleven popular JavaScript frameworks: React, React with Redux, Ember.js, Backbone.js, AngularJS, (new) Angular, Vue.js, jQuery, Preact, Inferno, and Flight. Many of these frameworks are used on the most popular websites in the world, such as Facebook and Twitter. The performance of these types of operations depends on the speed of the DOM APIs, the JavaScript engine, CSS style resolution, layout, and other technologies.

Peacekeeper

Peacekeeper is a platform-independent benchmark by Futuremark that tests rendering, mathematical and memory operations. It takes approx. 5 minutes for execution and tells the results of other browsers with different CPUs. Futuremark stopped maintaining Peacekeeper in July 2015.[2] The test was taken offline in March 2018 and is no longer available.

Testdrive

Microsoft maintains a suite of performance-oriented tests, often designed to test and stress JavaScript and rendering performance. These tests are typically designed to highlight IE's performance[citation needed], but are compatible with other major browsers.

WebXPRT

WebXPRT is a cross-platform browser benchmark that runs HTML5- and JavaScript-based workloads.[3] The benchmark provides scores for six individual workloads, as well as an overall score.[4] WebXPRT is published by the BenchmarkXPRT Development Community, which is administered by Principled Technologies, and is one of the BenchmarkXPRT benchmarks. WebXPRT 3 is the most current version of WebXPRT.[5]

3D tests

Wirple BMark

Performance test for HTML5 3D applications. It tests performance in both Canvas3D and WebGL.

Developer suites

Mozilla benchmarks

Dromaeo (superseded by Kraken)

A Mozilla test suite based on SunSpider tests. It takes several minutes for execution and displays very detailed information about every single test task.

Kraken (active)

Another JavaScript test suite from Mozilla, released September 14, 2010.[6]

Apple benchmarks

JetStream (active)

A JavaScript test suite developed by Apple.[7]

SunSpider (superseded)

SunSpider is a benchmark created by the webkit team that aims to measure JavaScript performance on tasks relevant to the current and near future use of JavaScript in the real world, such as encryption and text manipulation.[8] The suite further attempts to be balanced and statistically sound.[9]

Version 0.9 was released by the WebKit team in December 2007.[10] It was well-received,[11] and other browser developers also use it to compare the JavaScript performance of different browsers.[12]

Version 0.9.1 was released in April 2010.[13]

Version 1.0 was released in April 2013.[14]

Google benchmarks

V8 (superseded)

A JavaScript test suite by Google, used to optimize the Google Chrome web browser. It does not test rendering performance. It was superseded by Google's Octane benchmark.

Octane (unmaintained)

Google's JavaScript test suite which replaces the V8 benchmark. According to Google, "Octane v.1 consists of 13 tests, 5 new ones and 8 from the original V8 Benchmark Suite."[15] Octane v.2 supplanted v.1, consisting of "17 tests, four more than Octane v1."[16]

As of April 12 2017, Google no longer maintains Octane.[17]


GUIMark 2

This tests vector, bitmap, and text rendering for both Adobe Flash and HTML5.

References

  1. ↑ "Speedometer 2.0: A Benchmark for Modern Web App Responsiveness". 15 January 2018. https://webkit.org/blog/8063/speedometer-2-0-a-benchmark-for-modern-web-app-responsiveness/. 
  2. ↑ Brinkmann, Martin (23 July 2015). "Futuremark ends support for Peacekeeper benchmark". Ghacks. http://www.ghacks.net/2015/07/23/futuremark-ends-support-for-peacekeeper-benchmark/. 
  3. ↑ Hachmann, Mark (28 November 2018). "Samsung Galaxy Book 2 tablet review: Performance takes a back seat to battery life". PCWorld. https://www.pcworld.com/article/3323059/samsung-galaxy-book-2-tablet-hands-on-performance-takes-a-backseat-to-battery-life.html?page=3. 
  4. ↑ Addison, Ken (19 April 2018). "The Ryzen 7 2700X and Ryzen 5 2600X Review: Zen Matures". PC Perspective. https://pcper.com/2018/04/the-ryzen-7-2700x-and-ryzen-5-2600x-review-zen-matures/2/#ftoc-heading-8. 
  5. ↑ Cutress, Ian (5 November 2018). "Intel Xeon E Six-Core Review: E-2186G, E-2176G, E-2146G, and E-2136 Tested"". AnandTech. https://www.anandtech.com/show/13526/intel-xeon-e-review-e2186g-and-more-tested/8. 
  6. ↑ Jostedt, Erica (14 September 2010). "Release the Kraken". Mozilla. https://blog.mozilla.org/blog/2010/09/14/release-the-kraken-2/. 
  7. ↑ Heath, Nick (21 May 2015). "Windows 10 and Edge: How Microsoft's new browser could soon challenge Chrome". TechRepublic (California, USA). http://www.techrepublic.com/article/windows-10-and-edge-how-microsofts-new-browser-could-soon-challenge-chrome/. 
  8. ↑ Muchmore, Michael (18 June 2008). "Review: Firefox 3 Stays Ahead of Browser Pack". PC Mag.. http://www.foxnews.com/story/0,2933,368182,00.html. 
  9. ↑ "SunSpider JavaScript Benchmark". WebKit Open Source Project. http://www.webkit.org/perf/sunspider/sunspider.html. 
  10. ↑ Stachowiak, Maciej (18 December 2007). "Announcing SunSpider 0.9". WebKit Open Source Project. http://webkit.org/blog/152/announcing-sunspider-09/. 
  11. ↑ Atwood, Jeff (19 December 2007). "The Great Browser JavaScript Showdown". http://www.codinghorror.com/blog/archives/001023.html. 
  12. ↑ Resig, John (3 September 2008). "JavaScript Performance Rundown". http://ejohn.org/blog/javascript-performance-rundown/. 
  13. ↑ Stachowiak, Maciej (7 April 2010). "Announcing SunSpider 0.9.1". WebKit Open Source Project. http://webkit.org/blog/1046/announcing-sunspider-0-9-1/. 
  14. ↑ Stachowiak, Maciej (7 April 2010). "Announcing SunSpider 1.0". WebKit Open Source Project. http://www.webkit.org/blog/2364/announcing-sunspider-1-0/. 
  15. ↑ "The Benchmark—Octane". 22 August 2012. https://developers.google.com/octane/benchmark. 
  16. ↑ "The Benchmark—Octane". 6 November 2013. https://developers.google.com/octane/benchmark. 
  17. ↑ "Retiring Octane". 12 April 2017. https://v8project.blogspot.com/2017/04/retiring-octane.html. 



Retrieved from "https://handwiki.org/wiki/index.php?title=Browser_speed_test&oldid=3429890"