memes

Same with 8 GB of L1 cache.

Like a MacBook

What it feels like moving from x86 to ARM

• no one

Mine certainly isn't. 6GB vram, 16gb ram.

It depends on your definition of "usually", high end GPUs for data centers, AI, workstations or "enthusiasts" yea. For these applications you're starting at like 16

GPUs for us plebs, no

8gb of VRAM is still pretty good, but 8GB of RAM is getting pretty low these days. 16GB of ram and 6-8 VRAM is pretty common, and even that might go up relatively soon.

Creating your swap as 2x your RAM is outdated advice. Now it's essentially changed to be 2x until 4GB of RAM, then 1x until 8GB, and anything over 8GB just use 4GB of swap because you probably have enough RAM. Or, even some modern systems like Fedora will swap to zRAM. Which is just a highly compressed portion of RAM.

I remember being thrilled to move from floppies to a 16mb flash drive for my school assignments, even if I did have to constantly download and reinstall the USB Mass Storage drivers for the Windows 1998 sp2 computers in the library which reset every night. And the transfer speed was SLOW.

The fact that you can get a terabyte flash drive now, which can hold 62,500 of my school assignment drives, is mind blowing to me.

You should check out Linux live USBs from nearly 2 decades ago then.

When my dad first saw an nvme drive he had to triple check what he was looking at BC in his old 70s computer brain there's no fucking way something so small and unmoving can hold so much data, read/write it so fast, and all for a relatively cheap price.

Something I was able to do with my old OnePlus 3 phone, was use it as a Linux USB. It was a pretty neat trick!

It was really convenient to just snag a work laptop and boot it into Puppy Linux (which lives entirely in RAM) to browse around and such without my job looking too closely and being creepy about it.

The first one I used was 5MB. The OS on the machine (a CP/M version) didn't know how to handle it, so it was partitioned as lots and lots of floppies. Not very useful.

So I can boot up without a disk now?

Slow? Not necessarily.

The main issue with that much memory is the data routing and the physical locality of the memory. Assuming you (somehow) could shrink down the distance from the cache to the registers and could have a wide enough data line/request lines you can have data from such a cache in ~4 cycles (assuming L1 and a hit).

What slows down memory for L2 is the wider address space and slower residence checks. L3 gets a bit slower because of even wider address spaces but also it has to deal with concurrency issues since it's shared among cores. It also ends up being slower because it physically has to be further away from the cores due to it's size.

If you ever look at a CPU die, you'll see that L1 caches are generally tiny and embedded right into the center of the processor. L2 tends to be bolted onto the sides of the physical cores. And L3 tends to be the largest amount of silicon real estate on a CPU package. This is all what contributes to the increasing fetch performance for each layer along with the fact that you have to check the closest layers first (An L3 hit, for example, means that the CPU checked L1 and L2 and failed at both which takes time. So L3 access will always be at least the L1 + L2 times).

Mine got upgraded to a full meg.

8GB/s, or 8GB per month.