Major performance hit with 1.10.845.3
-
Originally I posted this in another thread but then I realized that this probably deserves its own thread.
I upgraded from Vivaldi version 1.10.838.7 to 1.10.845.3 recently and now it's incredibly slow. Vivaldi was quite CPU-hungry before but responsive nevertheless, but now it's really slow. Some pages take twice as long to load with the new version (just an estimate; I didn't measure this, but I can if it would help). On Windows 10 I'm on the same version and I didn't notice a regression there, although this machine is more powerful so I'm not sure if this is a Linux thing only.
This is probably unrelated to the new issue, but I want to mention it anyway: what I also noticed, I can play videos from Youtube with QMPlay2 with much less CPU use than with Vivaldi, so the high CPU use is definitely not a problem with my laptop per se.
-
@Pezo Hi. It might help for potential "community troubleshooting" of your problem if you include your relevant specs, eg, cpu, ram, distro, DE...
FYI, my V-SS [current version] continues to be lovely to use for me, same as SS's have been for a very long time [for me]. Maybe i'm just lucky... or maybe your issue is local to your installation rather than a generic V-SS-Linux fault.
..............................................................................................
Tower & Lappy = Maui Linux 17.03 x64 Plasma 5.9.3.
Vivaldi 1.10.845.3 (Official Build) dev (64-bit)
.............................................................................................. -
@Steffie Yeah you're right, I'm running Arch Linux (updated at least every few days) on a Dell XPS 13 9360.
Some specs: Intel Core i5-7200U CPU @ 2.50GHz (dual core), 8GB RAM, XFCE Desktop.
I haven't considered that package updates from Arch may have caused this, but since the older version runs fine that's unlikely. -
Generic reply to you both: i assume you've already tried all the "standard" troubleshooting stuff, such as:
- Toggling h/w accel from its current state. vivaldi://chrome/settings/search#hardware
- Testing with a clean profile
- Uninstalling all extensions [works hand in glove with #2].
?
-
So I've tested 1.10.845.3 10.10.850.1 and 1.10.850.1-1 (including email on the 850 versions - oops, did I give something away? - and, no, email is not about to be released) on an old Intel Core2 Quad, 2.8 GHz, Intel onboard graphics, 8GB DDR3 RAM, dual-boot machine. Tested it in Win10 Creators Update 64-bit and completely updated Linux Mint 18.1 Serena/Cinnamon 64-bit.
If anything, performance is at least as good and both CPU +-10% per core) and RAM usage (+-46%) are less than the last time I tested that machine on these platforms. (with a lot of tabs, it looks like RAM may be a little bit more, but CPU still less.
I don't have Linux on my main tower here.
-
@JSJB Have you tried changing hardware acceleration settings or anything? I can't get it to be "pathetic" on any of the 9 machines/OS'es here.
-
@JSJB Sometimes it's not OS+Hardware or Broswser+Hardware or Browser+OS, but Browser+OS+Hardware. It is, I fear, a fallacy to say that because this works, that should work.
The very fact that the browser seems perhaps unable to fully access the hardware on your OS is, to me, a clear indication of Browser+OS+Hardware. This is going to be quite difficult for the developers to reproduce, as they don't have you machine on a bench - and a wide variety of Linux users on .deb-based systems are having no trouble.
-
@Steffie said in Major performance hit with 1.10.845.3:
Toggling h/w accel from its current state. vivaldi://chrome/settings/search#hardware
You still should try this, not merely opine that it won't help or should not be necessary.
I am not doubting the sincerity of your problem, only that it is absolutely not generic across all or even most Linux V users, as best i can judge from these fora.
-
@JSJB I surmise from the fact that it is performing poorly and under-utilizing your resources, that it cannot, for some reason, use them. If it could, it would and it would perform better I think.
-
@JSJB I wouldn't know. I just update per the content of the Mint 18.1 repos.
-
@JSJB - Momentarily. I'll have to log out of Win10 on that machine and boot back in to Mint. And I'll have to change the wireless dongle as .deb Linux has "updated" drivers to where my good one no longer works on it.
-
@JSJB Mine is 2.23-0ubuntu7
-
@JSJB In the Vivaldi folder, I only have libffmpeg.so. I also have usr/lib/chromium-browser/libffmpeg.so and usr/lib/x86_64-linux-gnu/oxide-qt/libffmpeg.so
-
@JSJB Hi. Just to add a slightly different perspective, it might be helpful to have a look at the Changelog for this snapshot since one of the major changes could be the culprit.
First of all, there was an upgrade to the Chromium engine. This might be causing problems with an extension. Try disabling extensions and then selectively re-enabling them.
Vivaldi has also been making some UI enhancements. You could also try temporarily tuning off some Vivaldi features: uncheck "Use Animation" in Appearance settings, uncheck "Enable Tab Stacking" in Tabs, and uncheck "Allow Gestures" and "Allow Rocker Gestures" in Mouse settings. If that helped, try re-enabling them one by one.
It's also worth checking the status of vivaldi://gpu just to see if any errors are reported, or if your graphics card has been black-listed and/or the GPU process was unable to boot.
This is also a longshot but have you added any USB peripherals that might be causing problems with the underlying Chromium WebUSB code?
Lastly, do you start Vivaldi from a clean state or do you resume your previous session with lots of open tabs?
There could also be a profile issue, especially if you reverted to a previous version of Vivaldi and upgraded again. There could also be a problem with "Top Sites" file in your profile.
Sorry if I've repeated anything that's already being suggested and best of luck with with your troubleshooting!
-
@JSJB said in Major performance hit with 1.10.845.3:
The setting has checked "Use hardware acceleration when available" already and shows poor performance.
For the 3rd & final time i shall attempt this... i said "<<try>> Toggling h/w accel from its current state". TOGGLE = select the opposite state to its original state. I did NOT say "tick the box", but toggle it, ie, if it is already ticked, try unticking it, then rebooting. What do you have to lose?
Even if it makes no improvement, then you are still one step closer to a solution [everything we eliminate as potential root cause draws us inexorably closer to the real root cause... aka the Sherlock Holmes methodology]. Alternatively, though it might not be so for you, some other users have found their problems improved after toggling this setting.
-
Wow there's a lot going on here. To address a few things:
@Steffie No I haven't actually tried to start with a fresh profile. I can still do if you think it makes a difference.@xyzzy I didn't know about vivaldi://gpu, that's really interesting. I discovered that apparently all kinds of hardware acceleration were disabled, so I enabled the
ignore-gpu-blacklist
andenable-gpu-rasterization
flags, and now the newer version seems as fast as the old one, if not faster. The only thing on vivaldi://gpu that remains non-green is "Native GpuMemoryBuffers: Software only. Hardware acceleration disabled". I could post the content of that page if that would help...@Ayespy As you said you're on Mint, which I suppose is somewhat behind in kernel and libraries, it would maybe make sense to get a machine with Arch on it to test on the newest platform available.
-
@Pezo Just a word of caution on enabling
ignore-gpu-blacklist
-- the GPU got blacklisted by the Chromium developers (usually) for a very good reason, most likely to work around stability and/or performance issues. It also should not have been necessary to forceenable-gpu-rasterization
.Don't stress too much if any line items in the GPU status are non-green. The Chromium GPU stack has both hardware independent and hardware-specific components. The hardware acceleration code tries to leverage your GPU's capabilities as much as it can and also works around limitations where necessary.
Hopefully things will start working better for you. If you should run into any new issues, be sure to set these flags back to their defaults before you do any troubleshooting.
-
@JSJB I generally don't recommend changing any flags. You likely won't run into horrible breakage by enabling #ignore-gpu-blacklist but forcing any other GPU-related flags can cause major problems.
For the sake of my curiosity, what happens when you revert all of the flags except for the blacklist override?
Keep in mind too that under-the-hood Chromium-related changes might still be at play, and those are beyond Vivaldi's control.
-
-