How Companion.energy Reduced Query Latency 25x and Compressed Terabytes to Gigabytes with Tiger Cloud

Companion.energy migrated its real-time energy-optimization platform from Azure PostgreSQL’s limited TimescaleDB extension to managed Tiger Cloud after growing sensor volumes caused dashboard timeouts, slow latest-reading queries, storage pressure, and an unannounced Azure outage. After evaluating MongoDB, InfluxDB, and ClickHouse, the company retained its PostgreSQL-based architecture to gain TimescaleDB features including skip-scan, compression policies, continuous aggregates, managed observability, database forking, and LiveSync replication. The company reports that skip-scan reduced key meter-reading queries from 4,950 milliseconds to 202 milliseconds, columnstore compression reduced 1.7 TB of logical data to 39 GB of physical storage, and continuous aggregates now support energy-cost dashboards by precomputing data from an 807-million-row raw table. The eight-week migration replicated changes with low latency and was completed with a coordinated connection-string cutover, while the new setup separates market-data workloads from customer-facing operations. Companion.energy expects the platform to accommodate customers ranging from gigabyte to petabyte-scale data requirements without separating its workloads across multiple database systems or redesigning its core data model.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.