Remix.run Logo
anthonj 4 days ago

I see the problem, but I don't see a clear analysis on the actual source of the problem. I assumed the issue was mainly single core performance, but he is also suggesting context switches could be the cause?

So could you fix that with a new scheduler? Or you just need another SoC with better single core performance? I could imagine that the latter already exists, just not in soc with >16 cores. My naive view is that such high core count system comes with tradoff on core size and interconnect/memeory bus complexity.

And I mean.. my phone is a middle lower end device and for sure I can play youtube videos (maybe in a popup as well) and run the browser without noticing that much difference from my laptop.

KaiserPro 4 days ago | parent | next [-]

I think the single core performance would be bearable if it wasn't combined with maintaining a custom built kernel.

NavinF 4 days ago | parent | prev [-]

I don't think youtube playback is a relevant comparison since it uses ~0 CPU. Pretty much all phones have hardware accelerated decoding. Lots of TVs and streaming devices use an ancient Android phone SoC yet they too can play YT and run a browser. The entire UI is often a local web app.

anthonj 4 days ago | parent [-]

I imagine, be he mentions video playback on youtube making things worse, and he does have a dedicated amd gpu.

But iirc for both Firefox and chromium on Linux desktop hw acceleration is tricky so maybe it's that.

NavinF 3 days ago | parent [-]

Yes anything GPU related other than CUDA is a shit show on Linux desktop. Another issue is that YT loves to use AV1 if they know you're on desktop. Almost all desktop users have a CPU powerful enough to software decode it in realtime, but if you're on a prebuilt PC you'll definitely notice the fans kick in

theevilsharpie 3 days ago | parent [-]

I can't speak for Firefox, but Google Chrome (and presumably anything Chromium-based) has working hardware-accelerated video on AMD and Intel GPUs.

It does admittedly take some effort to set up; I assume Google is hesitant to enable it by default because of issues with Nvidia GPUs. But when configured, it works and has for years.