• 6 Posts
  • 118 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle




  • Just to add as we are discussing mainly ARM vs x86 now… that is just a small part of the whole device. Just look at the SD OLED vs LCD. They managed to have OLED screen that is significantly better than the LCD one while using less power on AVG which is a huge deal to battery life and it either allows you to compensate with more power to SOC to achieve better performance at the same battery life or take the saving and go with higher battery life… and that’s just screen.

    Then they optimized the PCB layout, PCB components, etc… to get both better cooling and efficiency.

    I think that what is currently holding them back is both the SOC available and the actual efficiency of given parts combined. Getting improvement in both areas at once will lead to a significant change but one or the other alone will not tip the scales towards significant upgrade.




  • Nothing yet surpassed Zen2 low power efficiency in the SD. And by low power I mean under 10W power/performance.

    New chips scale quite a bit better above 10W though.

    Also I’m not sure if that’s actually the HW limitation or just Valve tuning of the power behaviour. It’s possible they can throw in Zen5 and tune it to that efficiency level while getting significant performance uplift over Zen2 at the same power.

    Regarding GPU we will need much faster memory support to get any significant advantages even with RDNA4 as most iGPUs are starved for memory bandwidth anyways, not saying that RDNA4 wouldn’t be an improvement, just that it won’t be as big as a leap as it could be with faster memory.


  • Thanks. That’s a good ELI5. Fortunately I managed to make sense of it before your reply but the link to environment variables is highly appreciated. As I already replied to someone else, I had no idea PATH was a global/environment variable and just assumed it’s telling me to specify path so I had no idea I need to RTFM as it confused me greatly and on top of that I did another mistake which confused me even more when I finally managed to get it to do correctly which made me think I am doing it wrong.

    I gave up at CMAKE finally as I really need to RTFM more on that as it started to throw many errors at me.


  • I’m fine with RTFM but I had no idea PATH is a global variable and I assumed it’s telling me to specify path to something. So I had no idea I need to RTFM because I did not RTFM to understand that I need to RTFM. After the first reply pointed me the right direction I managed to make sense of it. Though english is not my first language and some of the terms are just over my head so I had to RTFM with dictionary which took a lot of time for me to finally understand because I was doing another thing wrong on top of that which specifically was

    I had to do ~/SCALE_PATH instead of the confusing example of $(SCALE_PATH} as trying nvcc --version did absolutely nothing even though the path was correct

    I’ve been on Linux since April so I’ve stumbled a lot but got many things to work, it just takes me a lot of time to get trough it and I’ve really stumbled on this one. Getting ROCM to work was a breeze and most recently getting PyTorch with ROCM to work for AI generative models on AMD. I’ve also finally started to tinker with toolbox a lot more and finally understand the benefits of it.











  • Please bear in mind that custom tuning isn’t a guarantee between different driver versions; the voltage floor can shift with power management firmware changes delivered driver packages (this doesn’t overwrite the board VBIOS, it’s loaded in at OS runtime (pmfw is also included in linux-firmware)). I’d recommend testing with vulkan memory test with each Adrenalin update, and every now and then on Fedora too.

    I’m aware. For now it seems to behave consistently. I observed higher avg clocks on Linux vs Windows with the same OC but then again it may be due to difference in monitoring SW or just polling rate.