cancelDec 4
All the "memory is cheap" developers can truly shut the fuck up now.
Show threadARGVMI~1.PIFDec 5

@cancel

Thankfully Linux people don't seem to have that attitude. Even the big bells-and-whistles desktop environment will run comfortably on 4GB.

Show threadLudovic :Firefox: :FreeBSD:Dec 5
@argv_minus_one @cancel back 20 years ago, 4 gb is fing HUGE
Show threadRTG-powered VelDec 5

@usul while Vel wasn't alive 20 years ago, it's quite certain that low end devices were not using 1920x1080@60 24-bit displays. triple-buffering wasn't used, since there were no fancy smooth animations, etc

using more RAM is often for the purposes of speeding things up and ultimately reducing the load on the CPU/GPU/disk.

@argv_minus_one @cancel

Show threadcancelDec 5

@risc @usul @argv_minus_one

macs were triple buffered by default in 2001 (mac os x) windows was triple buffered by default in 2006 (vista)

Show threadRTG-powered VelDec 5
@cancel got it, apologies. should have checked.
@usul @argv_minus_one
Show threadcancelDec 5

@risc @usul @argv_minus_one

don't worry it's not that big of a deal.

Show threadCurioDec 5

@cancel
Something is different though. On our laptop almost half the RAM is used by the iGPU driver's RAM spillover. This was not the case 5+ years ago.

That (and websites getting fatter) are the main reason it regularily OOMs.

Got any info/hypothesis on that?
@risc @usul @argv_minus_one

Show threadRTG-powered Vel

@curiousicae sounds like either a bug or strange settings... vel's iGPU only gets any significant amount of RAM when it's actively using something heavy

@cancel @usul @argv_minus_one

Dec 5 at 2:39pmWeb
Show threadcancelDec 6
@risc @curiousicae @usul @argv_minus_one yeah usually you allocate a small amount of fixed memory for the iGPU in BIOS for software which can't dynamically allocate it for some reason (certain old APIs?) and then allow the GPU driver to carve out more memory for graphics from shared as needed using the proper APIs.
Show threadCurioDec 6

@cancel
Most of the used memory is “GTT” (horrible Linux kernel jargon for “RAM dynamically allocated by the GPU” - took me years to understand that radeontop line).

I think the static assignment is actually for the iGPU, so that it can function without the graphics driver being present.

Seems like its feeling modest right now though (usually GTT is easily twice that) – really doubt AMD fixed anything for a “legacy” GCN 1.0 card in their driver suddenly:
@risc @usul @argv_minus_one