Search posts, papers, and topics
2 posts · blog.timescale.com
This guide explains how to evaluate the trade-off of adding a composite index in PostgreSQL by quantifying its read benefits and write costs. It provides a method to measure the impact on ingest throughput and decide if the index earns its overhead based on your system's peak ingest ceiling.
A Python exporter reads Meshtastic mesh telemetry from MQTT and writes it directly into a TimescaleDB‑enabled PostgreSQL instance, replacing a Prometheus setup that hit ~0.5 M series for 10 k nodes. The single database lets Grafana dashboards join node metadata with eight time‑series tables in one query, eliminates scrape‑budget limits, and uses native retention/compression (14‑day compression, 3…
