Attributed metadata history
Up to 100 retained publisher events per page for 8d1656556aec879fce5364dde1f357b3ec887ceccc62558cb42e362af73e3993. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_42bd4a24749d327e8d
observed · 2026-10-14 21:35:03 UTC
Highlights Runs on a 256 MB Raspberry Pi The trail update needed ~1.1 GB and was OOM-killed on small boxes, and the sensor needed 153 MB, twice that across a trail reload. Measured in a 221 MB container with no swap, against the full 1.9M-trail set: 3.4 3.5 trail update (peak) 1,144 MB 69 MB sensor (steady) 153 MB 32 MB sensor during a reload 304 MB 58 MB The static trail set is streamed from its cache instead of being held in memory whole: the update peaks at ~255 MB on every machine now, not 1.1 GB. Below 768 MB available (container and systemd limits included), the merge spills to a SQLite file. Same code, byte-identical trails.csv. UPDATE_SERVER downloads stream to disk. The sensor's trail store is file-backed (reclaimable page cache instead of heap); lookups measured the same speed. Hosts with under 1 GB get a capture ring of 10% of RAM instead of 64 MB. Thanks to @gpaterson for the report and the idea (#19641). 32-bit ARM sensor New static ARMv6 build, arm-unknown-linux-musleabihf: one binary for every 32-bit Raspberry Pi, Pi 1 and Zero included, on Raspberry Pi OS, DietPi or Alpine. install.sh picks it automatically, also on a 64-bit kernel with a 32-bit use
Fingerprint: a87041d52722702ffabcfc0cccf02836ce92cd3f808615bbc58523f7674e1ddb
intelligence_src_42bd4a24749d327e8d
observed · 2026-10-12 09:17:03 UTC
available
Fingerprint: a3b0c36a677e1deaa5104d098bcd3f49d623f73969b2ffbc57a48cc705a29c9f