Website Resource Utilization of User's Client PC

[moriel5]

One of the main reasons why I had moved to Invidious (other than the privacy concerns), was Polymer YouTube's atrocious system resource utilization, which is why I tried to hold on as long as possible onto the old polymer-free YouTube.

Back then, I had an i3-540 (nowadays I use an i5-4570 with a Radeon HD6950), and I was able to play 1080p60fps with barely any stutters, however with the polymer theme, anything above 720p30Hz was unpractical.

Additionally, we have a BayTrail Celeron Chromebook (dechromified), that used to be able to play 720p30fps without any stuttering on the old pre-polymer YouTube, however with the polymer YouTube, anything above 240p is unplayable due to the stuttering.
With Invidious, Even 720p60fps/1080p30fps is playable with minimal stuttering, however with Piped, I cannot go above 480p due to the stuttering.

Could something be done about this? Possible a "lite" version of the website (possibly with the Invidious GUI above the Piped backend)?

[FireMasterK]

I don't understand how this is possible at all, from my testing Piped uses a lot less CPU and memory than Invidious even when streaming at 4k.

In this image, I was streaming with 4k on Piped and 1080p on Invidious (due to the lack of a 4k option).

Please report back with your findings on about:performance.

[moriel5]

No problem, I'll do so as soon as I can.

[moriel5]

I made a mistake, due to the whole mess phone manufacturers have made with aspect ratios, I compared a 1080p (960p) stream to a 720p (640p) stream.

My performance results from that dechromified laptop back your results, and interestingly, 1080p barely required anything beyond 720p on Piped, however it still stuttered a bit more than Invidious (I'm guessing due to the network connection, I get the same thing with your Invidious instance when compared to others).

Results:

Piped (1080p)

• CPU: ~7.4-10, Peak at 11.1
• RAM: ~15.8, Peak at 22.5
  Namazso Invidious (720p)
• CPU: ~12.2-12.9, Peak at 25.8
• RAM: Kept on rising, and I stopped at 93.1

Should this be closed as invalid?

In any case, even Invidious has a hard time playing 1080p30fps now, though it isn't as severe (probably due to network connection) as Piped.

[FireMasterK]

Thanks for the findings! It's good to know that this isn't a serious issue.

About the differences you noticed, it could be possible that it was because you didn't enable dash on Invidious.

[moriel5]

Thanks for the findings! It's good to know that this isn't a serious issue.

About the differences you noticed, it could be possible that it was because you didn't enable dash on Invidious.

Nope, I did.
I have to so manually at each new browser session, since Privacy Redirector isn't applying my settings there (And I can tell, since I also change the theme with this instance from dark to light).