Recommended Posts

I tried Firefox HA mode and it just make Firefox dramatically slowed down. The UI rendering is so laggy and the web rendering of youtube when scrolling is considerable laggy too. Firefox renders and scrolls youtube fine when HA is off. IE9 renders youtube normally so can anyone explain the reason Firefox is so horrible at it? Or why bother with HA at all if it doesn't actually render Firefox faster?

Well, it might be due to several reason, I personally also victim of it so I am not gonna defend Firefox but you can do several things to reduce impact of Hardware Acceleration.

1) Update your driver

2) Tweaking settings in about:config

Also can you tell me your addons list, might be some addon making your UI so slow. Firefox improved a lot since FF7 onward. FF13 is quite snappier than any earlier version.

Well, it might be due to several reason, I personally also victim of it so I am not gonna defend Firefox but you can do several things to reduce impact of Hardware Acceleration.

1) Update your driver

2) Tweaking settings in about:config

Also can you tell me your addons list, might be some addon making your UI so slow. Firefox improved a lot since FF7 onward. FF13 is quite snappier than any earlier version.

My addons are of the usual ones like adblockplus, greasemonkey,firebug,flashgot,User Style Manager, etc. I set my graphic driver to be updated automatically so it shouldn't be a problem. Firefox feels pretty snappy with HA off, so it must be their HA mode that slow it down.

What setting are you refering to in the config?

It's because FF HA mode is still young and hasn't matured hence why software mode works much better they've done all they can to make it fast and stable now it's time to try using something other than the CPU alot of browsers that are starting out with GPU acceleration are having problems with either speed or stability or both and like anything new it takes time to become good

I'm running a laptop with C2D T9300 and Nvidia 8600M GS with latest driver 296.10.

Today there are chances of new driver release, so make sure to update. I personally had issues with 296.10 so I am using currently 301.40 and it is much better than 296.10. Also new driver will be from same branch as 301.40.

Also should I suggest you once try Nightly for a while and tell us whether you feel any difference?

I was reading the Opera release thread and apparently they are offering both OpenGL and DirectX options. Is it posible that Mozilla could do the same? DirectX seems to be superior at doing HA in IE9 compare to OpenGL in Firefox. Does anyone have a lead on Mozilla HA's developement?

Firefox's hardware acceleration already uses DirectX (Has since 4.0), OpenGL isn't used by default because a bunch of cheap cards have either terrible or no support for it.

I've got a GTX 570 with full OpenGL support for the latest version, but Firefox still doesn't use it.

Firefox HWA is terrible because, (research! "lurksearch" {tm})

  1. Developers focus on Smart Phone Version
  2. Developers focus on Panorama, Smooth WebM playback and other things of little value.
  3. Developers do not have any way to test D3D10 performance for some reason, otherwise they would know it is slow.
  4. Most Developers use Macs.
  5. Aside from a developer called Bas, I don't know anyone who talks about Windows HWA.
  6. Developer's solution to Windows HWA problems is a BLACKLIST.
  7. Last performance improvement for HWA was Azure in FF7 which does NOTHING for helping YouTube, tab scrolling, etc.
  8. I also heard that a lot of rendering that is supposed to be accelerated falls back to software for GUI.
  9. They probably just don't care.

I was reading the Opera release thread and apparently they are offering both OpenGL and DirectX options. Is it posible that Mozilla could do the same? DirectX seems to be superior at doing HA in IE9 compare to OpenGL in Firefox. Does anyone have a lead on Mozilla HA's developement?

Well, Firefox already offer both Hardware Acceleration but Skia backend (OpenGL) can only turned on for canvas hardware acceleration. Azure Content Acceleration will be Nightly (FF15) turned, which is better than Cairo backend but it still uses Cairo as a backend but it is still better.

  • 11 months later...

Firefox HWA is terrible because, (research! "lurksearch" {tm})

  1. Developers focus on Smart Phone Version
  2. Developers focus on Panorama, Smooth WebM playback and other things of little value.
  3. Developers do not have any way to test D3D10 performance for some reason, otherwise they would know it is slow.
  4. Most Developers use Macs.
  5. Aside from a developer called Bas, I don't know anyone who talks about Windows HWA.
  6. Developer's solution to Windows HWA problems is a BLACKLIST.
  7. Last performance improvement for HWA was Azure in FF7 which does NOTHING for helping YouTube, tab scrolling, etc.
  8. I also heard that a lot of rendering that is supposed to be accelerated falls back to software for GUI.
  9. They probably just don't care.

I agree, when I used firefox on a linux recovery disk, it runs so much smoother than the windows version.Also firefox has a page where they classify the various versions, the classification affects how much dev focus it gets. Its notable that the windows version of firefox is not in the top classification.Trying to find the url now with the info but I found this out when looking for why is no 64bit windows version and then discovered because they dont treat windows as that important.Its sad but they consider mobile platforms and even metro as more important than 64bit windows desktop version.http://www.computerworld.com/s/article/9234997/Mozilla_compromises_on_x64_Firefox_after_user_backlashLinux and even mac os (a OS I consider irrelevant on desktop) have 64bit firefox. For whatever reason firefox dev's treat windows as a 2nd class OS.Firefox is probably my most power hungry app, it draws mroe resources from my PC than even some games, right now its using 1.1gig of ram and a 32bit version can only address 2 gig. It also crashes often and slows down a lot, I remain curious if these issues would be resolved with a 64bit version, as now days a browser is not just for web pages, its used as a launcher for apps and multimedia.On the Hw acceleration this is highlighted a lot.Firefox 3 using software rendering runs very smooth, but of course it doesnt support many of today's modern web features. However if disabling hw acceleration in firefox 20 (or any new version) the software mode is slower than it was in firefox 3's day because it now has no focus on it plus features are been added that bog it down. Hardware mode is smooth if the 3d card is moderatly powerful and isnt throttled back. using firefox puts a lot of load on my nvidia card, it hits high temperatures and is often on 3d clocks, it I use an app to force the card to stay in 2d idle mode (which Ie can handle) firefox becomes jerk city, it struggles to even scroll pages like neowin forums. It is extremely power hungry and clearly not very optimised.See this alsohttp://arstechnica.com/information-technology/2012/11/64-bit-firefox-for-windows-should-be-prioritized-not-suspended/Here is the link for dev priority, found it. Windows 64 tier 3. linux 64 tier 1.https://developer.mozilla.org/en-US/docs/Supported_build_configurations

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Because Chrome is doing it. And no one said anyone had to update immediately. That's silly. They could update every day for all I care as long as it's fast, and the next time the browser restarts, you're good. And the basic point is not to tee it up for bigger updates. As it is right now, all the windows I had open reopen anyway except inprivate.
    • Why? Does anybody actually want this? The constant need to close all browser sessions and wait for a new version to install, just so that there’s a integrated coupon manager feels like a waste of everyone’s time
    • I remember when Louis used to just do interesting Mac/iPhone repairs, now he's boring and just launches "crusades" every week
    • A shame it don't allow people to bypass the MS account, I will stick to using Rufus.
    • Microsoft about to radically change how often your Edge browser updates by Paul Hill Microsoft has just announced that starting with Edge 152, it will be moving to a two-week release cycle for faster, smaller updates. This faster release cadence will begin on August 27. This change comes just several months after Microsoft switched Visual Studio Code to weekly updates. The company said that the Extended Stable releases will remain on an eight-week cycle and that no admin changes are needed to experience the faster release cycle on the Stable channel. The new two-week release cycle will enable the faster delivery of security updates and platform improvements, all while reducing the size and complexity of individual updates. Microsoft claims that organizations will benefit from this change as it offers predictable validation cycles. For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option. This change will affect Edge Stable releases on Windows, macOS, Linux, and mobile. The Extended Stable channel will continue to be updated every eight weeks, or every fourth Stable release, for example: versions 152, 156, 160, and 164. The Extended Stable could be a good option for organizations that don’t want the latest updates twice a month and don’t want as much hassle constantly updating browsers. In the case of Visual Studio Code, many of the updates being pushed by Microsoft are AI-related. As we all know, Microsoft Edge has a lot of AI features, so we could see Microsoft pushing more AI, thanks to the faster cycles. On the flip side, quicker releases could mean faster security updates, which is beneficial in a world where AI systems are hunting for software exploits. What do you think? Let us know in the comments. For more updates on Edge, be sure to follow Neowin's coverage. In May alone, we reported on Edge offering in-browser pop-ups to assist users with website compatibility issues, that Edge was losing Copilot Mode, and that Microsoft had fixed a plain-text password bug in Edge. Source: Microsoft 365 Admin Center
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!