Analysis

The disk you buy for local models is not the disk that runs them

A buyer guide to portable SSDs for GGUF weights, Hugging Face caches, and the overflow a laptop boot drive cannot hold. The shop cards are two SanDisk Extreme listings. Artificial Examiner has not bench-tested either drive. The links are affiliate.

Server racks in a CERN computing room, photographed 25 February 2009. Photo by Florian Hirzinger, CC BY-SA 3.0, via Wikimedia Commons.
Photo: Florian Hirzinger / Wikimedia Commons (CC BY-SA 3.0)

A laptop runs out of disk before it runs out of ambition. The operating system, the browser, a container runtime, and one careless Hugging Face snapshot will fill a 512 GB or 1 TB internal drive, and then the weights you actually wanted will not fit. A portable SSD is the shelf for that overflow: GGUF files, hub caches, and datasets you would rather not fetch twice. It is not extra RAM, and it is not extra VRAM.

The cards under this story are affiliate links. If you buy through them, Artificial Examiner may earn a commission. We have not bench-tested either drive. The capacity math below does not depend on which listing you click.

Buy the shelf for the files you will keep. The sticker speed is a ceiling your port may never reach.

What the library actually weighs

Treat the next paragraph as planning arithmetic, not as a stopwatch result from this desk. For a dense model, a 4-bit GGUF lands on the order of half a gigabyte per billion parameters. An 8-billion-parameter quant is a few gigabytes. A 32-billion-parameter quant is in the high teens of gigabytes. A 70-billion-parameter Q4 file is on the order of 40 GB. The same 70 billion parameters stored as FP16 or BF16 safetensors are on the order of 140 GB, before the tokenizer, the extra shards, and the copy you kept until the conversion looked right.

Mixture-of-experts files do not shrink to the “active” parameter count in the announcement. The disk holds every expert. A model that feels small while it is generating can still be a large file.

The hub cache is where a terabyte goes to die. The default Hugging Face cache keeps snapshots. Download a revision, download someone else’s quant of the same repo, leave both, and you have stored the weights twice. If the internal SSD is the boot volume, point the cache at the portable drive. HF_HOME is the variable that moves the tree. The hub cache sits underneath it. A symlink from ~/.cache/huggingface to a folder on the external volume does the same job when you do not want every shell to carry the variable.

Ollama keeps a separate store. OLLAMA_MODELS moves that store. llama.cpp does not have a cache to relocate. You pass the path to the GGUF. Desktop apps that hide the path usually expose a model-folder setting. Put the library on the portable drive, and leave the internal SSD for the operating system plus the one file you are loading this week, if that file fits.

A labeled terabyte is not 1,024 gibibytes of free space. Drive makers sell decimal terabytes. A device labeled 1TB is about 931 GiB before the filesystem takes its slice. Leave headroom. A volume that is actually full gets awkward for the program writing the next snapshot, and it leaves you no room to unpack a download before you delete the old one.

Why the boot drive is the wrong shelf

The internal SSD is the right place for the operating system, and for the single model you are loading today when it fits. It sits on the laptop’s own PCIe link. There is no cable, no hub, and no volume that vanishes because the lid moved. That path is faster and steadier than USB. Use it for the working file.

It is a bad warehouse. Plenty of machines ship with a drive the OS and the apps have already claimed, and plenty of thin laptops solder that drive in place. Filling it makes updates, sleep, and swap miserable. A portable drive is how you keep a library you can carry to the other computer without cloning the machine.

The trade is that the link can disappear. Loaders memory-map a GGUF. A cable that slips, a hub that cannot feed a bus-powered drive, or a volume that sleeps mid-read looks like a corrupt model. Often the file is fine and the disk is simply gone. Do not keep the only copy of a long download on a drive that lives in a bag. If you cannot fetch it again, copy it somewhere else before you trust the portable shelf.

What the port will actually do

One card below is the SanDisk 1TB Extreme Portable SSD, up to 2000MB/s, new model. The phrase “up to 2000MB/s” is the figure in that listing’s title. It is the maker’s rated ceiling. This desk did not time the drive. Two thousand megabytes a second is 16 gigabits of payload. A USB-C port that only speaks USB 3.2 Gen 2, at 10 gigabits a second, cannot deliver that ceiling. A lot of laptop ports are exactly that port. On those machines you are buying shelf space. You are not buying the number in the title.

The other card is the SanDisk Extreme Portable SSD, 2TB, black, new model. Its listing title, as we are using it, does not print a separate speed. Do not assume the 1TB title’s ceiling transfers. Both are portable USB-C solid-state drives in the same new-model line, and both cards use the same product photo, because that is the image on the variation listing. On a 10-gigabit port they will be limited by the port, whichever capacity you pick.

A Thunderbolt 3 or 4 jack is a 40-gigabit port. Plugging a USB portable SSD into it does not turn the drive into a Thunderbolt device. The drive speaks USB, at the fastest USB mode the port and the drive both support. USB4 jacks are not all the same speed. Read the spec for the socket you will actually use. Some laptops put a fast port on one side and a slower one on the other, and the charger side is not a promise about the data side.

Use the short cable that comes in the box, or another cable rated for the same USB generation. A charge-only lead can fall back to USB 2. A large GGUF over USB 2 takes long enough that the loader looks broken. These are bus-powered drives. The port, or the hub in front of it, has to supply power. A hub that looks fine and starves the device will drop the volume in the middle of a write. That is how a half-written snapshot becomes a file you have to delete.

Format once, on purpose. exFAT is the practical choice if the drive will move between macOS and Windows. Use APFS if the library never leaves a Mac, and NTFS if it never leaves Windows. Copy everything off before you reformat a disk that already holds your only snapshot. On Linux, exFAT is the least annoying format to share with the other two.

If a long load stalls and then continues, check disk sleep and USB selective suspend before you throw the file away. A portable SSD’s controller will idle. A memory-mapped read does not enjoy the nap.

When 1TB is the buy, and when it is not

Other portable SSDs exist. This guide’s cards are only the two listings we can attach to a real Amazon Associates tag, threadandfade-20. We are not ranking them against each other or against any drive we cannot link. There is no price in this piece, because a price we did not check today would be a fiction by tomorrow.

Choose the SanDisk 1TB Extreme Portable SSD, up to 2000MB/s, new model when the library is quantized files a laptop can actually run, and when you delete old hub snapshots. Dozens of small GGUF files, several mid-size ones, and a handful of 70-billion-parameter quants fit in that shelf with room left, as long as you are not also hoarding every BF16 original. It is the right capacity for one person using the drive as overflow and pruning it.

Choose the SanDisk Extreme Portable SSD, 2TB, black, new model when you keep the hub download and the converted GGUF, more than one quant of the same large model, or a dataset you refuse to fetch twice. It is also the better shelf when two machines share one library. It is still a shelf. A 2TB drive does not let a 16 GB laptop run a model that does not fit in memory. Disk holds the weights. Memory runs them. If you cannot load the file, the second terabyte is an archive, and you should decide you want an archive before you buy one.

Neither card is a review. Artificial Examiner has not opened these boxes, has not measured a sequential read, and has not loaded a GGUF from either SKU. The blurbs under the story say that in shorter form. Check the seller, the return window, and the cable in the box the way you would for any other storage purchase.

The buttons under the article go to those two Amazon listings with our Associates tag. They are advertisements. The commission, if a purchase happens, does not pick the capacity. The files you intend to keep do.

This story includes affiliate links. If you buy through them, Artificial Examiner may earn a commission. That does not change the reporting. See our affiliate disclosure.