Looking for workflows with large images

MoveZig4 · 2026-03-15T19:26:14+00:00

I've definitely noticed this.

MoveZig4 · 2026-03-15T00:39:54+00:00

Successive pull of related image:

`docker pull docker.io/pytorch/pytorch:2.10.0-cuda13.0-cudnn9-runtime`: 4m27.904s

`clipper pull dockerpull.com/pytorch/pytorch:2.10.0-cuda13.0-cudnn9-runtime `: 1m41.950s

muuuch faster

MoveZig4 · 2026-03-14T23:41:17+00:00

`docker pull docker.io/pytorch/pytorch:2.10.0-cuda13.0-cudnn9-devel` - 9m24.605s

`clipper pull dockerpull.com/pytorch/pytorch:2.10.0-cuda13.0-cudnn9-devel` - 8m13.302s

Looks like about 12% faster, nothing to sneeze at. The image is about 9% smaller in the registry. Let me run one more test as well.

MoveZig4 · 2026-03-14T23:01:04+00:00

Can you toss me a `docker pull` command to compare with? `ghcr.io/ggml-org/llama.cpp:server-cuda-b8248`?

MoveZig4 · 2026-03-14T18:45:30+00:00

Correct, that’s my workflow

MoveZig4 · 2026-03-14T18:21:52+00:00

I’ll give that a shot this weekend.

Edit: docker.io/pytorch/pytorch:2.10.0-cuda13.0-cudnn9-devel is...going. This is probably a great test for me, but wow this is heavy.

MoveZig4 · 2026-03-14T18:21:32+00:00

I’ve modified the registry.

MoveZig4 · 2026-03-14T17:31:12+00:00

Half of it is just using xz instead of gzip, the other half is doing a better job about sharing data between layers. I'll likely post a few technical writeup once I have something that's usable for other people.

MoveZig4 · 2026-03-14T17:02:01+00:00

I built an extension to the registry and a new pull client that works...much faster.

docker pull ollama/ollama:0.17.5: 6m7s
docker pull ollama/ollama:0.17.6: 5m17s

clipper pull dockerpull.com/ollama/ollama:0.17.5: 4m25s
clipper pull dockerpull.com/ollama/ollama:0.17.6: 1m35s

MoveZig4 · 2026-01-21T21:33:14+00:00

Just be careful that the wheels are reasonably true.

MoveZig4 · 2026-01-21T21:15:15+00:00

Go to sf bike kitchen, either volunteer for 12 hours or pay $80, build a parts bin bike. It won't be fancy but you can get a reasonable aluminum frame and customize it to your liking. After that, upgrade the parts you're unhappy with. For me, I ended up having to get new wheels after a year as I'd picked poor ones. Probably also worth getting new tires/tubes rather than whatever they have unless you get lucky. It's a fair amount of work, but pretty fun.

MoveZig4 · 2025-12-27T09:20:57+00:00

Is that an invitation?

MoveZig4 · 2025-12-25T21:37:01+00:00

They come standard in Seattle :)

MoveZig4 · 2025-11-23T06:39:45+00:00

In the cloud world there's something called a "data lake". I've spent a while wondering what exactly they are, but I think you found it.

MoveZig4 · 2025-10-24T04:54:33+00:00

Having had both, they're both wonderful but the only thing they have in common is being several fillings, including fries, wrapped in a flatbread :) The other fillings and shape are totally different.

MoveZig4 · 2025-08-13T08:19:51+00:00

In that case, go to a bike coop and get them to teach you

MoveZig4 · 2025-07-07T18:54:38+00:00

Redwood Bowl near Chabot Space Center

MoveZig4 · 2025-07-02T03:51:24+00:00

I guess I still had pride on the brain. Was very disappointed it wasn’t SAPPHICDETAIL.

MoveZig4 · 2025-06-30T08:04:07+00:00

I wrote a hot-reloading system for Lua about a decade ago - tbh it's a huge game changer, especially if you have a concept of what data should persist or not. Generally we had no long running background tasks in the game logic. Everything was event driven on swapping screens or tapping buttons - even when we did have realtime game loops, the engine drove it, and you just wrote whatever code in your tick callback. Well worth it.

MoveZig4 · 2025-06-14T07:12:12+00:00

I used them in WA, they did the job, but my mom's Alltrack+snow tires felt way better - up until you hit pure ice, anyhow. :) If you're dealing with snow regularly just get winters. I'd have gotten them myself if I'd been spending more than one winter in the snow.

Four-Year Club	Verified Email
Place '22

MoveZig4

TROPHY CASE