<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Timeseries on SensorRig — Real Raspberry Pi Sensor Monitoring</title><link>https://sensorrig.com/tags/timeseries/</link><description>Recent content in Timeseries on SensorRig — Real Raspberry Pi Sensor Monitoring</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 03 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sensorrig.com/tags/timeseries/index.xml" rel="self" type="application/rss+xml"/><item><title>Why SQLite in WAL Mode Is the Right Database for a Pi Sensor Logger</title><link>https://sensorrig.com/posts/sqlite-wal-sensor-logging/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate><guid>https://sensorrig.com/posts/sqlite-wal-sensor-logging/</guid><description>I run a Raspberry Pi 4 as a 24/7 home sensor logger — basement temp/humidity, per-room heating, a solar shed node, whole-house power, and a server rack. That&amp;rsquo;s six data sources writing continuously. I needed a database that:
survives a power cut without corrupting, handles thousands of small inserts per hour, doesn&amp;rsquo;t need a separate server process, and lets me keep years of rollups on a single SD card. After parallel-running it against my old RRDtool setup, I landed on SQLite in WAL mode.</description></item></channel></rss>