Originally posted by Ermine
View Post
Announcement
Collapse
No announcement yet.
Firefox Nightly Tries For VA-API Video Acceleration For Mesa Users
Collapse
X
-
-
Originally posted by birdie View Post
I wanna see the actual proofs of that. A blog post made by someone who's in the topic will suffice. I remember X11 drawing primitives were GPU accelerated but those haven't been used by anything in Linux for more than a decade.
Qt Quick (you can see MangoHUD visible on the window)
non-Quick Qt (no MangoHUD visible)
The sad part is that only few applications use Qt Quick (parts of KDE System Settings and Discover do for example), which means the rest is still CPU based :<
Comment
-
Originally posted by tildearrow View Post
I don't think this will be enough, but:
Qt Quick (you can see MangoHUD visible on the window)
The sad part is that only few applications use Qt Quick (parts of KDE System Settings and Discover do for example), which means the rest is still CPU based :<
- Likes 1
Comment
-
Originally posted by tildearrow View Post
I think it's more like Mozilla not caring about Linux consumers because the userbase is small when compared to Windows.
To give you an idea of the complexity of this work just check out this bug which I helped figure out a couple of weeks ago. We hit crashes related to sandboxing NUMA controls that were coming from a major distro but not using its standard packages... for video decoding. This stuff is hard and takes a lot of time in order for it to be both stable and secure.
- Likes 7
Comment
-
Originally posted by tildearrow View Post
[B]Nope, I have not said or thought this.Last edited by user1; 04 June 2022, 05:10 AM.
Comment
-
I suspect you simply have too much spare time complaining about stuff that doesn't matter much, see also implicit vs. explicit rendering discussion.
Firefox Wayland GPU performance is fine vs. Windows, as is Plasma Wayland desktop performance. VAAPI decoding efficiency is fine vs. Windows D3D11VA. Do you even test and use stuff, or skip directly to useless complaints?
Btw. basic drawing operations with few shapes and lines are already insanely fast on any CPU, kind of proves my point...
- Likes 1
Comment
-
Originally posted by crystall View PostWe hit crashes related to sandboxing NUMA controls that were coming from a major distro but not using its standard packages... for video decoding.
Comment
-
Originally posted by aufkrawall View PostBtw. basic drawing operations with few shapes and lines are already insanely fast on any CPU, kind of proves my point...
- You're on mobile, battery life matters. A LOT.
- You have your GPU active (you're compositing after all).
- This activity would mean minimal load for a GPU, which means it's unlikely to overclock, so it won't drain more energy.
- This activity, while fast on fast CPUs, means greater load for them, as they're not specialized, so it'll likely keep them from going into lower power states.
- Your battery drains faster.
And that's something I factually noticed over the years on dual boot computers: battery tends to last longer on laptops when running Windows, at least in my experience.
Acceleration is not only about speed, it's also about using specialized hardware to achieve better power efficiency.
- Likes 3
Comment
-
Originally posted by sinepgib View PostAnd that's something I factually noticed over the years on dual boot computers:
I got dualboot Windows & Arch on that Gemini Lake 2C CPU notebook and even with slow conservative CPU clock governor and strict 6W TDP enforced on Linux vs. 12W on Windows, performance while browsing the web, files, watching videos etc. is just massively better with Plasma Wayland vs. Windows 10/11.
Sorry, but if you think there really would be a major performance drawback in real life due to differences in GPU acceleration of Linux vs. Windows, you're simply clueless. I basically got the shittiest "modern" SoC out there and the results just speak for themselves. You're chasing ghosts, that's all I got left to say. I can't take this seriously, sorry.Last edited by aufkrawall; 04 June 2022, 06:47 PM.
Comment
Comment