Summary: | DoYouEvenBench: Add tests WebKit is slow on so WebKit is not fastest when we start optimizing | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | andersca, barraclough, benjamin, darin, fpizlo, ggaren, kling, koivisto, syoichi |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Ryosuke Niwa
2013-09-19 23:26:11 PDT
God damnit, we should stop doing such a good job optimizing WebKit :) Maybe you could consider: -Gaming frameworks? (https://github.com/mrdoob/three.js/, Box2D, LimeJS) -Mobile frameworks? (http://jquerymobile.com/) -Charting frameworks? (http://raphaeljs.com/, http://livedocs.dojotoolkit.org/dojox/charting). -Various Polyfills (Mozilla Brick?). The interesting part is, it would show if a native implementation bring much benefits to the browsers implementing it. All of them have demos. Maybe the demos can be made into something useful for performance tracking? Firefox 24 beats us! Firefox 24: 5991.2 ms Firefox 24 is faster than Nightly build of WebKit. The problem solved! |