On 12/14/2012 05:01 AM, MCBastos wrote:
> Interviewed by CNN on 14/12/2012 10:43, MCBastos told the world:
>> I recently ran into this blog post by Nick Cameron:
>> 
>> <http://featherweightmusings.blogspot.com/2012/12/how-to-win-benchmarks-and-influence.html>
>> 
>> It's an interesting read about artificial benchmarks, but on checking
>> the results in my computer one thing sprang out:
>> I got very good results in Firefox 17, but very poor results in
>> Seamonkey 2.14. From Cameron's explanation, the difference is related to
>> whether the browser is using Windows Direct2D or not.
>> 
>> I thought that (using Direct2D) was a Gecko feature that is shared
>> between Firefox and Seamonkey. Am I wrong? Or is it a matter of flipping
>> the appropriate switches in about:config?
>> 
> 
> Addendum: apparently it was the about:config option
> gfx.direct2d.disabled that was set to "true."
> I reset it to the default value, and it became "false," and the
> performance in the suspect benchmark improved noticeably. I suppose
> other rendering will become faster too.
> 
> Thing is, I don't really remember having tweaked that option. It might
> have happened one or two years ago and I have forgotten about it, of
> course. But still...
> - Does anybody remember if there was ever a legitimate reason for
> disabling Direct2D?
> - Was it default in earlier versions of Seamonkey (perhaps some known
> problems)?
> - If so and if the issue has since been fixed, shouldn't upgrades flip
> on Direct2D?
> 

Perhaps at some time you were testing?
<https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#How_to_force-enable_blocked_graphics_features>

BTW: I use linux & that option isn't available. Checked this page (it
was on the 'return to' page & easier to see the fps):

<https://ie.microsoft.com/testdrive/Performance/Bubbles/>

Linux:
 Firefox 17.0.1: 2 - 0 fps (starts at 2 fps & then drops to 0)
 SeaMonkey 17.0.1: 2 - 1 fps (starts at 2 fps & then drops to 1)
(both drive Xorg to 93% cpu & bring the system nearly to a dead stop)
 Opera 12.11: constant 5 fps. Opera drives the cpu to ~70%, but doesn't
screw up Xorg, Xorg stays around 18%. The system is still workable.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to