Guide | Vivaldi on 🐌 Old / Low End Computers

Zalex108

@edwardp said in Guide | Vivaldi on Old / Low End Computers:

@Zalex108 The display resolution should also have an effect. I have the resolution set to 1920x1080, which is Full HD. The monitor is a 22-inch Samsung.

IDK,
Those are Laptops, both 1366*768, Intel I5 HD3000 works fine, intel I5 HD5000 has that problem.

But still needs to be checked with more attention.
Connecting it to an external FHD didn't noticed that behaviour when recently connected.

edwardp

@Zalex108 I switched the resolution to 1680x1050 (16:10) today and will also be testing it at this resolution.

edwardp

Had an online meeting through Jitsi.

On the desktop (13 years old) with the specs shown below, having both the GPU rasterization (#enable-gpu-rasterization) and Enable ProcessPerSite up to main frame threshold (#enable-process-per-site-up-to-main-frame-threshold) flags enabled, I noticed the combined CPU usage between (what I call) the two main Vivaldi processes (on Linux, KDE desktop), was around 50% or so. This was with the display resolution set to either 1680x1050 (16:10) or 1920x1080 (16:9).

Without any flags enabled previously, it would show 100% CPU usage all the time when on Jitsi.

Setting these two flags in Vivaldi for this desktop's hardware, is clearly making things better. The graphics quality on Jitsi was also better

Zalex108

@edwardp

Saw this "GPU limit" flag few days ago.
I'll test it here.

Thx

Whatever to keep computers snappy.
I remember the flag related to "Cache on Ram"

Why deprecated?
Even having a SSD those R/W count.

Companies forcing the "Planned Obsolescence"

edwardp

@Zalex108 I found a post online that on an older MacBook Pro, enabling the #enable-drdc flag (Enables Display Compositor to use a new gpu thread), the interface on that Mac became snappier.

When enabled, chrome uses 2 gpu threads instead of 1. Display compositor uses new dr-dc gpu thread and all other clients (raster, webgl, video) continues using the gpu main thread. – Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros

So I have enabled it here and am testing it out, leaving the above referenced flags enabled.

(Originally, this flag was specific to Android, but is now available for all operating systems.)

edwardp

In testing video before an online meeting, I noticed there was a delay in the video with the #enable-drdc flag enabled. Once it was reset to the Default setting (disabled), the video returned to normal, so I am now leaving this flag disabled.

edwardp

I did some research regarding the GPU in the newer desktop (specs in signature). It does not support GPU Rasterization, or Hardware Acceleration (HWA), so I have reset the gpu-rasterization flag back to Default (disabled) and turned off HWA.

Zalex108

@edwardp

Try the --in-process-gpu switch

nVidia 520M

GPU

edwardp

@Zalex108 --in-process-gpu seems to be specific to Wayland. I mostly use X11.

edwardp

With KDE Plasma 6 on Linux, using X11, I have turned off the Floating switch in the Panel Settings and found Vivaldi, as well as the overall KDE interface, now run faster.

I have Hardware Acceleration turned on in the Vivaldi Settings, as well as the ignore-gpu-blocklist flag enabled.