someone's avatar
someone 1 week ago
nos.lol db size 587 gb pruning older, less important, low WoT ones

Replies (16)

Always actually wondered who ran those relays, at 587 gb that's one hell of a service you've provided.
someone's avatar
someone 1 week ago
thanks. i should do a better job. like automating this pruning ๐Ÿ˜ƒ
pnk's avatar
pnk 1 week ago
How long did it take to grow to that size?
This should be highly compressible, especially with a dictionary zstd
someone's avatar
someone 1 week ago
3+ years i pruned a few times before
pnk's avatar
pnk 1 week ago
So one could easily run a relay on a 1TB phone
Or put the database on ZFS. But. There is always a but. ZFS is a cow filesystem, it may be slower, but it may actually be faster because of the compression. Everything depends on the underlying hardware
Zstd dictionanaries should be small, max 1MB, and often 128kb to keep zstd fast. If every klient pulled such dictionary once a few months, all event data could be kept and served compressed, very efficiently. This is probably what FB does in it's client? Compression is underrated, we have very fast cpus now, very fast algos like zstd, proper setup will actually increase the client speed and decrease the network data being sent
someone's avatar
someone 1 week ago
yes compression looks doable. maybe even tell my clanker to do deflate because then there is no decompression, directly serving to clients over websockets.
โ†‘