Difference between revisions of "Firefox Performance Testing Lab Fall 2010 kclascon"
(→Test Notes) |
(→Test Notes) |
||
(One intermediate revision by the same user not shown) | |||
Line 41: | Line 41: | ||
| [http://www.chromeexperiments.com/detail/colorscube/ Colorscube] || Kevin Lasconia || 09/16/2010 || The rotating animation on the cube appeared to be faster in Chrome. || The rotating animation was considerably smoother in Chrome. || There appeared to be a slight delay during the when doing the rotation gesture in Firefox. Chrome had no delay. || Overall, Chrome completely outperformed Firefox for this experiment. Bother browsers had similar CPU usage. | | [http://www.chromeexperiments.com/detail/colorscube/ Colorscube] || Kevin Lasconia || 09/16/2010 || The rotating animation on the cube appeared to be faster in Chrome. || The rotating animation was considerably smoother in Chrome. || There appeared to be a slight delay during the when doing the rotation gesture in Firefox. Chrome had no delay. || Overall, Chrome completely outperformed Firefox for this experiment. Bother browsers had similar CPU usage. | ||
|- | |- | ||
− | | [http://www.chromeexperiments.com/detail/js-touch/ js touch] || Kevin Lasconia || 09/16/2010 || | + | | [http://www.chromeexperiments.com/detail/js-touch/ js touch] || Kevin Lasconia || 09/16/2010 || No noticeable speed differences between browsers. || Bother browsers seem to be equally as smooth. || Both browsers had similar response times when moving the mouse. || Overall, the experiment seem to perform equally in both browsers. |
|- | |- | ||
− | | [http://www.chromeexperiments.com/detail/multiplayerchessorg/ Multiplayerchessorg] || Kevin Lasconia || 09/16/2010 || | + | | [http://www.chromeexperiments.com/detail/multiplayerchessorg/ Multiplayerchessorg] || Kevin Lasconia || 09/16/2010 || N/A || N/A || N/A || This experiment in currently down. |
|} | |} |
Latest revision as of 10:51, 17 September 2010
Contents
Test Results (kclascon)
Hardware Info
- Adapter Description: ATI Mobility Radeon HD 4530
- Vendor ID: 1002
- Device ID: 9553
- Adapter RAM: Unknown
- Adapter Drivers: atidxx32 atidxx64 atiumdag atiumdva atiumd64 atiumd6a atitmm64
- Driver Version: 8.563.1.3000
- Driver Date: 2-9-2009
- Direct2D Enabled: false
- DirectWrite Enabled: false
- GPU Accelerated Windows: 1/1 Direct3D 9
Firefox Build Info
Mozilla/5.0 (Windows NT 6.0; WOW64; rv:2.0b7pre) Gecko/20100916 Firefox/4.0b7pre
Chromium Build Info
7.0.528.0 (59761)
Test Notes
Name & URL | Tester | Date | Firefox Performance - Speed | Firefox Performance - Smoothness | Firefox Performance - Responsiveness | Notes and other Details |
---|---|---|---|---|---|---|
Twitch | Kevin Lasconia | 09/16/2010 | No noticeable speed differences between browsers. | No noticeable smoothness differences between browsers. | Both browsers appear to be equally responsive to the mouse clicks. | The only glaring difference between the browsers for this experiment is the CPU usage. Firefox ranged from 20% - 24% CPU usage while Chrome range from 10% - 15% CPU usage. |
Browsermation | Kevin Lasconia | 09/16/2010 | The animation at full speed (Holding down Ctrl+Tab) appeared to be faster in Chrome | The animation at full speed appeared more fluid/smooth in Firefox. It is "jerky" in Chrome. | When switching between tabs, Chrome appeared to have a faster response time. | It appears to be speed vs. smoothness in this experiment. The CPU usage can also reflect this. At full speed Firefox ran at 49% - 54% CPU usage. Chrome on the other hand had a fluxuating CPU usage of 51% - 93%! |
Browsertalk | Kevin Lasconia | 09/16/2010 | When I talked, the "mouth" appeared to move at similar speeds in Firefox, and Chrome. However, when launching the experiment Chrome started considerably faster then Firefox. | The "talking" animation appeared smoother in Chrome when it picked up my voice. | There seemed to be a slight delay from when I talked and when the mouth moved in Firefox. Chrome seemed to be more responsive. | Overall, I think Chrome outperformed Firefox for this experiment. CPU usage for both browsers were similar. |
Domtris | Kevin Lasconia | 09/16/2010 | No noticeable speed differences between browsers. | No noticeable smoothness differences between browsers. | Both browsers were equally responsive when changing the direction of the block, and dropping the block. | Both browsers performed equally. CPU usage was relatively low for this experiment in both browsers. |
Browser Ball | Kevin Lasconia | 09/16/2010 | No noticeable speed differences between browsers. | The bouncing animation of the ball appeared very similar in both browsers. I would say Chrome was a tad bit smoother. | Firefox had some issues with this experiment. When additional windows were spawned, if you tried to drag the ball into these windows it would get stuck. This did not occur in Chrome. | I would say Chrome performed better than Firefox due to the ball issue with multiple windows. CPU usage is something to take note of though. Firefox ran at a very constant ~22% CPU usage. Chrome on the other hand ran at around 38% - 50% CPU usage. |
Gravity | Kevin Lasconia | 09/16/2010 | Does not work in Firefox. | Does not work in Firefox. | Does not work in Firefox. | Experiment worked perfectly in Chrome. |
Monster | Kevin Lasconia | 09/16/2010 | No noticeable speed differences between browsers. However, when grabbing the 3D object the animation would slow down in Firefox. | Overall the animation appeared to be more fluid in Chrome. It was a bit choppy in Firefox when more complex objects were used. | When grabbing the objects and rotating them it was more responsive in Chrome. In Firefox there would be a slight pause before responding. | Overall Chrome outperformed Firefox for this experiment. Firefox had constant 54% CPU usage. Chrome had a constant 44% CPU usage. |
Colorscube | Kevin Lasconia | 09/16/2010 | The rotating animation on the cube appeared to be faster in Chrome. | The rotating animation was considerably smoother in Chrome. | There appeared to be a slight delay during the when doing the rotation gesture in Firefox. Chrome had no delay. | Overall, Chrome completely outperformed Firefox for this experiment. Bother browsers had similar CPU usage. |
js touch | Kevin Lasconia | 09/16/2010 | No noticeable speed differences between browsers. | Bother browsers seem to be equally as smooth. | Both browsers had similar response times when moving the mouse. | Overall, the experiment seem to perform equally in both browsers. |
Multiplayerchessorg | Kevin Lasconia | 09/16/2010 | N/A | N/A | N/A | This experiment in currently down. |