[fastest963]

Why does the Harbor VM need 32 cores and 64GB of RAM? Especially if it's only serving 32,000 pulls over 2 months.

[Symbiote]

For what it's worth, I have an on-prem Nexus server with a Docker repository. It has 8 cores and 16GB RAM. It has 82000 hits/day in the webserver log, though 99.9% of them transfer only a few kB, so I assume it's a metadata check and the client already has the correct version.

The same Nexus is also hosting our Maven and NodeJS repositories. That has 1,800,000 hits per day, although all but 120,000 of them return HTTP 404. (I think one of our clients has misconfigured their build server to use our Maven repository as a mirror of Maven Central, but as it's just an AWS IP I don't know who it is.)

I'm sure it's overprovisioned, but the marginal cost of 2, 4 or 8 cores and 4, 8 or 16GB RAM isn't much when we buy our own hardware.

[nchmy]

> the marginal cost of 2, 4 or 8 cores and 4, 8 or 16GB RAM isn't much when we buy our own hardware

this is the crux of it all. RENTING bare metal (eg from hetzner) is 10x cheaper than aws ec2. So, I can only imagine how much cheaper it is when you buy the hardware directly.

[01HNNWZ0MV43FF]

I want something like "This could have been an email" but "This could have been a Caddy instance and static files"

Hell Git doesn't even need the Git protocol if you do `update-server-info`

[mcpherrinm]

It does seem mostly possible to host a Docker registry with static files and a bit of config:

https://github.com/jpetazzo/registrish

I haven’t tried running this yet, but it seems worth keeping in mind. It’s relatively simple software so the idea could probably be pretty easily adapted to other situations.

[adolph]

I recall mentioned here ttl.sh, which as I looked it up [0], uses through Docker a CNCF project called Distribution Registry [1] which implements the core container registry functions (and appears to have additional utility, like being a pull-through cache).

0. https://github.com/replicatedhq/ttl.sh/blob/main/registry/en...

1. https://distribution.github.io/distribution/

[arccy]

It's certainly possible with s3, so probably for any other static host https://news.ycombinator.com/item?id=40942732

[nchmy]

It does seem like a lot. Though, it's also a rounding error for them. It is probably sized to optimize for something else than just $

[nodesocket]

Agree that seems insanely inefficient. That's less than a pull a minute.

[maratc]

FWIW,

   > During this time, Harbor has served more than 32,000 pulls under company-wide use in day-to-day business.

It is possible to read this as the "32,000 pulls" is a daily number, not a total one.

[marginalia_nu]

Even if it is a daily number, it's not very much. There are 86,400 seconds in a day. Even limiting the time to an 8 hour business day, this is only around 1 pull per second.

[mystifyingpoi]

> Why does the Harbor VM need ...

They never say that it needs these resources, they say that the current VM has this config. Probably overkill by 1000%.