Open main menu

CDOT Wiki β

Changes

Firefox Performance Testing Lab Fall 2010

496 bytes added, 21:51, 22 September 2010
Resources
== Resources ==
 
===Links===
* [http://chromeexperiments.com Chrome Experiments]
* [https://spreadsheets.google.com/ccc?key=0AgzO6h8d9PSsdHE0a2JmeEZWUHFOQm00ZTJLNElIZ2c&hl=en&pli=1#gid=0 Results Spreadsheet]. Talk to Dave to get permissions in order to edit.
* [http://nightly.mozilla.org/ Firefox (i.e., Minefield) nightly builds]
* [http://build.chromium.org/buildbot/snapshots/ Chrome (i.e., Chromium) nightly builds]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=594920 Example performance bug]
===Misc Info===
 
One of the questions that comes up a lot when filing these bugs, especially on Windows, is whether or not you have Direct2D (i.e., D2D) or Direct3D (D3D) enabled. The graphics system in Firefox has 3 states related to hardware acceleration:
 
# no hardware acceleration
# D3D but not D2D
# All hardware acceleration
 
You can control this using various preferences, which you can change by going to '''about:config''' (type this into your address bar and press enter):
 
* D3D Layers Preferences
** layers.accelerate-all
** layers.accelerate-none
* Font Rendering
** gfx.font_rendering.directwrite.enabled
* Direct2D
** gfx.direct2d.force-enabled
== Tests: Initial First Round ==