Open main menu

CDOT Wiki β

Changes

Firefox Performance Testing Lab Fall 2010 ajcondinho

2,272 bytes added, 14:04, 16 September 2010
Test Notes
[[Firefox_Performance_Testing_Lab_Fall_2010 | '''Go back to lab page''']]
=== Hardware Info ===*Adapter Description:ATI Mobility Radeon HD 4570 *Vendor ID:1002*Device ID:9553*Adapter RAM:512MB*Adapter Drivers:ATI Technologies Inc.*Driver Version:8.673.0.0*Driver Date:11/10/2009*Direct2D Enabled:Enabled*DirectWrite Enabled:Enabled*GPU Accelerated Windows:Yes
==Firefox Build Info==
Mozilla/5.0 (Windows NT 6.1; rv:2.0b7pre) Gecko/20100916 Firefox Nightly Build/4.0b7pre
==Chromium Build Info==
Chromium
7.0.527.0 (Developer Build 59649)
===Test Notes===
{| border="1" cellpadding="5"
!Name & URL !! Tester !! Date !! Firefox Performance - Speed !! Firefox Performance - Smoothness !! Firefox Performance - Responsiveness !! Notes and other Details
|-
| [http://www.chromeexperiments.com/detail/bomomo/ Bomomo] || Andrew || - 9/16/2010 || - CPU was sitting at approximately 50%, and showed no signs of lag. || - Visual components all seem to flow seamlessly. || - Using the first drawing tool the balls seem to be a bit behind on mouse movements. || -When tried out on Chrome, CPU use rose to 70% at idle, and a lot of lag occurred, Firefox seems to outperform Chrome on this experiment.
|-
| [http://www.chromeexperiments.com/detail/kaleidscope/ Kaleidscope] || Andrew || - 9/16/2010 || CPU usage varied from 30- 50% constantly. || - Ran smoothly, no jittery jumps. || Might be a bug, the actual window seems to jerk around while trying to re- size. || Chrome performed almost identically minus the re-sizing issue.
|-
| [http://www.chromeexperiments.com/detail/vizeddit/ Vizeddit] || Andrew || - 9/16/2010 || - CPU sat at around 50%. || - The Reddit alien seemed to stutter a bit on the way down. || - As far as I could tell this experiment doesn't actually allow you to do anything. || Chrome seemed to use 10-20% less CPU.
|-
| [http://www.chromeexperiments.com/detail/chiptunecom-gui/ Amiga Workbench Emulator] || Andrew || - 9/16/2010 || - See Responsiveness. || - See Responsiveness. || This experiment re- creates an old operating system, but upon "loading" it internally crashes, so I cannot actually test this one. || -Chrome loaded it and ran the experiment fine.
|-
| [http://www.chromeexperiments.com/detail/wavy-scrollbars/ Wavy Scrollbars] || Andrew || - 9/16/2010 || - Experiment not available for Firefox. || - Experiment not available for Firefox. || - Experiment not available for Firefox. || -Runs smoothly in Chrome.
|-
| [http://www.chromeexperiments.com/detail/javascript-canvas-raytracer/ Javascript Canvas Raytracer] || Andrew || - 9/16/2010 || - CPU was stable at 50%. || - This is a rendering experiment, so it took time to render it, so the image appeared slowly. || - Experiment responded quickly. || -Chrome ran just as fast.
|-
| [http://www.chromeexperiments.com/detail/notcanvas/ NotCanvas] || Andrew || - 9/16/2010 || Doesn't seem to be an actual experiment just shows results from pre- rendered drawings. || Doesn't seem to be an actual experiment just shows results from pre- rendered drawings. || Doesn't seem to be an actual experiment just shows results from pre- rendered drawings. || -Same in Chrome
|-
| [http://www.chromeexperiments.com/detail/internetris/ Internetris] || Andrew || - 9/16/2010 || - Low CPU usage (20%) || - Very smooth for Tetris. || - All controls were very responsive. || -Chrome ran exactly the same.
|-
| [http://www.chromeexperiments.com/detail/starfield/ Starfield] || Andrew || - 9/16/2010 || - CPU sat at 50% || - Very smooth. || - Very responsive to mouse clicks. || -Chrome used up 20% more CPU.
|-
| [http://www.chromeexperiments.com/detail/physicsketch/ physicSketch] || Andrew || - 9/16/2010 || - CPU sat at 50% || - Animations were very smooth. || - I encountered a problem when some of my drawings stopped showing up and I could not longer draw on the screen. It also seems to carry not allow me to draw anymore even if I reload the window, not sure if this is a problem on just my system. || -Did not get this error in Chrome.
|}
1
edit