- User Since
- Aug 9 2017, 12:25 PM (302 w, 6 d)
Sep 19 2020
They are both about compressing memory, so I believe results should be rather close
Sep 18 2020
@DataDrake Does this look meaningful enough?
Sep 11 2020
One more benchmark - https://linuxreviews.org/The_Benefits_Of_Having_A_Compressed_zram_Swap_Device_On_Linux
Jun 27 2020
Now I have latest bios 1.32, in auto mode a bit more that 1 Gb of memory is used for VRAM.
So it just works now, do not know why it did not.
Thank you everyone!
May 30 2020
Some thoughts about auto mode for VRAM. I expect that in this mode OS should be able to know in some way that it needs more VRAM and ask it from bios in runtime. Is that how it happens? If yes, than maybe this logic is broken?
Well, default uefi settings, 512 mb VRAM helped for now at least with memory, thank you! I am writing from Solus Firefox, which means it will work fine at least until I reboot it.
But again, I think that problem with memory is another case. If I will catch this bug how can I debug it? Please notice that sometimes I could not even enter console with ALT + Fx. Right after login it works fine, but executing almost any app would SOMETIMES crash system. Any browser, software center, eopkg upgrade or even update crashed in most cases just with "terminated" without any stacktraces. But upgrading package by package worked in the end. It seemed like any networking was causing that, but probably it was smth else.
Wow, what a coincidence with laptops). I will try to change settings in bios, but Solus was unusable LONG before bios update. I guess it was kernel 5.3 when i first noticed that. I hoped it some kernel regression and will be fixed soon in mainline but I was wrong.
So now it seems like we have 2 problems here, and I dont even know which one is more serious.
BTW, now VRAM setting is AUTO, will write about bios experiments shortly.
Thank you for your answer!