#
✕ nick:alih
#asahi · 2024-08-03 17:29
alihthat did resolve it for me, thanks
#asahi · 2024-08-03 17:24
alihi am also encountering the same
#asahi · 2024-07-16 00:03
alihmaybe the problem is just firefox? Because the kwin_wayland and plasmashell processes are otherwise a lot more comparable on the two laptops
#asahi · 2024-07-16 00:02
alihPaulFertser: as an example I just took an old laptop I have (with Arch+Plasma) and my M1 Mac. I created a new profile for Firefox on both (mkdir temp; firefox -profile temp/ -new-instance) and the numbers I'm reporting here are from top. On my m1 mac the topmost firefox process takes 717.0m RES 224.3 SHR. On my old amd64 laptop it takes 456.8m RES and 272.4M is shared.
#asahi · 2024-07-15 15:06
alihI understand, as it's shared on the apple arm architecture. I just wanted to know if there were ways to make KDE take less so that I could have a similar feeling of stretching out my multitasking capabilities as I do with Sway, but I realize this is probably not the right place to ask about KDE specific questions
#asahi · 2024-07-15 14:51
alihlots of memory is shared, but lots more is not
#asahi · 2024-07-15 14:50
alihmostly i'm looking at Mem/Swp in Htop, and per process I'm looking at RES and SHR
#asahi · 2024-07-15 14:49
alihplasma monitor, htop, zramctl, and such
#asahi · 2024-07-15 14:47
alihSo generally I'm finding Asahi to be really cool but I find that equivalent software takes more RAM than it does with its x86_64 counterparts. To counteract this I tried Sway which works works really great but I miss certain KDE Plasma features... so are there tips on how to make KDE use less RAM so I get fewer purple flickers in Firefox and such?