yarnd for example has a builtin weekly job that ensures feeds on a pod are kept under 1MB in size (configurable) and are rotated when they exceed this. Pods will also refuse to fetch feeds over this size too.
yarnd for example has a builtin weekly job that ensures feeds on a pod are kept under 1MB in size (configurable) and are rotated when they exceed this. Pods will also refuse to fetch feeds over this size too.
yarnd. Is there a way to see the full history of a feed? I don't see a prev metadata tag on yours.
$ curl -v -o /dev/null https://twtxt.net/user/mckinley/twtxt.txt 2>&1 | grep -i 'Content-Length'
< content-length: 107361
$ curl -v -o /dev/null https://twtxt.net/user/mckinley/twtxt.txt 2>&1 | grep -i 'Content-Length'
< content-length: 107361
to give things a perspective, try measuring the time of running curl on top1m even on a fast link it can be up to 1s
slow per say, one has to take into account pulling the feed into the cache layer and having payload rendered in a browser. the round trip of data from out in the wild back to the server involves network calls (cpu-bound), cache-stuffing (cpu+memory-bound), and disk read/writes. by the time it's done it can be a costly operation compared to a db-backed data store.