<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Retention on SensorRig — Real Raspberry Pi Sensor Monitoring</title><link>https://sensorrig.com/tags/retention/</link><description>Recent content in Retention on SensorRig — Real Raspberry Pi Sensor Monitoring</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 29 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sensorrig.com/tags/retention/index.xml" rel="self" type="application/rss+xml"/><item><title>SQLite Rollups and Retention: Stop Your Sensor DB From Eating the SD Card</title><link>https://sensorrig.com/posts/sqlite-sensor-downsampling-retention-sd-wear/</link><pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate><guid>https://sensorrig.com/posts/sqlite-sensor-downsampling-retention-sd-wear/</guid><description>If you keep every raw row from six data sources forever, SQLite grows linearly and your queries eventually crawl. The fix isn&amp;rsquo;t a new server — it&amp;rsquo;s rollups + a retention policy, with a hard look at what actually wears an SD card.
The measured baseline My Pi 4 logger writes continuously: basement temp/humidity (DS18B20 1-Wire + DHT11), per-room heating (5 Google Nest thermostats via the SDM API), solar shed node (ESP32-C3 over HC-12 433 MHz), whole-house power (CT clamps with ADS1115 ADC), an INA219 rail monitor, and a server rack.</description></item></channel></rss>