Quote from: vladk on December 29, 2023, 09:18:35nd useless for my use ( web, code , office work)
You probably made a mistake when typing the text, because... It is in these areas that built-in gpus are more than redundant.
The problem is that until now, x86 consumption when decoding video is several times higher than the consumption of smartphones, i.e. x86 is extremely inefficient in this regard.
This is what we have to fight against.
Moreover, sneaky Google (first of all) deliberately disables hardware decoding in new browsers for W10. I recently updated a 2019 laptop with Zen+ (3500U), installed 2023 drivers, the latest from AMD and the latest Chrome browser version 120 (and Chrome has always had a minimal load on the cores and the built-in gpu, compared to other browsers, except Edge, previously, but Edge has also switched to Chromium and therefore no longer makes sense to use) and what did I find in the M$ W10 Pro installed from the ISO from the site (and under LTSC 1809) - in the GPU task manager tab, now when playing a video there is no load in the Video Decode window (both in Pro and LTSC, but it was visible before), only 3D works, and the total load on the cpu+gpu has increased significantly. I install back the AMD driver 2020 (May) and the Chrome browser version 99 - everything works fine, with Chrome up to about version 100, then the api for working with VLD decoders through the layer for browsers (MF wrapper for VP9, which is built into Home/ProEducation) is apparently disabled ),
but it is missing out of the box in LTSC versions, so it must be installed from the MS application store - VP9 Video Extensions (by the way, it is paid there, but there is a free version, which few people know about).
Google is now using a different scheme that refuses to work with normal 2019 hardware (Lenovo supports this series of laptops until 2026).
In Firefox, hardware acceleration still works, but there, traditionally, the load even with hardware acceleration is much higher than in Chrome. Firefox is only good for software video decoding (on machines where there is no hardware support for VP9 decoders) - then the load on the processor and gpu is sharply lower than with software decoding in any version of Chrome. Therefore, on machines without hardware VP9, I always use Firefox (besides, it disables the incorrect muddy font smoothing, unlike Chrome from version 50, where it cannot be disabled and is much better for the eyes) and recommend it to friends who have old hardware without a hardware VP9 decoder .
The funny thing is that on an Intel c i5 8300H with Intel 2018 drivers, all versions of Chrome work normally with hardware video decoding on YouTube in VP9, on the gpu built into the processor. Both under W10Pro and LTSC 2019/2021.
That is, the fact that Chrome does not work correctly with built-in AMD 2019 gpus, even with the latest versions of drivers from 2023 and the latest version of Chrome under W10, is both AMD and Google's fault.
Intel also had its history of meanness - for example, earlier in 2010 they deliberately disabled the DVXA/DVXA2 decoder in XP (although everything was actually supported there), as a result, hardware acceleration did not work in XP even in players. And in W7 it worked disgustingly. Intel actually forced customers to upgrade to W7 when they didn't need to.
Since then, nothing much has changed, there are constantly secret agreements and meanness to refuse support for still current (and officially supported OS versions) in order to deliberately squeeze people into OS versions that are more profitable for them, now under the crooked and buggy W11 (which has up to there is still no stable build of the kernel, because they still have not released the LTSC version)
Quote from: vladk on December 29, 2023, 09:18:35Do we hit the Moore's barrier so that no improvement could be done ?
We are almost there; Moore's "law" has long since died. The performance growth curve per 1W has been flatter for several years now compared to what it was 10-15 years ago.