IceWeasel gets destroyed by Chromium in hardware acceleration stress test...
I try to use IceWeasel more than Chromium, but often find myself using Chromium more because it feels faster. I thought it was because I had too much stuff open in IceWeasel or because it gradually uses more RAM over time, but today I was getting really frustrated when pressing edit on a DokuWiki page was causing a CPU to churn at 100% for 15-20 seconds. I know I have old hardware (ThinkPad X60 with SSD and 3GB RAM), but... Chromium doesn't blink doing the same things.
Then, the results from this hardware acceleration stress test were insane:
- IceWeasel: 2 FPS
- IceWeasel (safe mode): 3 FPS
- Chromium: 60+ FPS (the limit of the test)
Something is seriously wrong... I'm hoping it's something I can fix...
Claes Wallin (韋嘉誠), Claes Wallin (韋嘉誠), Efraim Flashner, Efraim Flashner shared this.
- IceWeasel: 60+ FPS
- Chromium: 60+ FPS
jrobertson at 2015-12-28T16:50:31Z
Claes Wallin (韋嘉誠), Blaise Alleyne likes this.
I do not notice that behavior, and I use both. Platform or version may be relevant. :-(
For me they run comparably so I mostly use Iceweasel.
Thanks all. There's gotta be something with my setup for the performance to be so wildly different... I'll keep digging.
For posterity, fiddling around with information from here and here, I managed to get IceWeasel to perform at 25-30 FPS by forcing Option "AccelMethod" "sna" in my xorg.conf.
Also noticed IceWeasel was a lot snappier on a fresh user account, so probably need to close a ton of the tabs I have open (doesn't affect FPS performance though once IceWeasel's all loaded).