New installs use DuckDB for history
Fresh installs use DuckDB for history. Existing SQLite data can be moved through an explicit conversion flow. This update supports growing histories and longer-range aggregation.
| History length | SQLite(legacy format) | DuckDB(new installs) |
|---|---|---|
| 30 days | 72.0MiB | 16.9MiB |
| 90 days | 216.3MiB | 50.1MiB |
| 1 year | 883.3MiB | 202.7MiB |
Synthetic-data comparison: the DuckDB column shows the median across 3 builds, about 76–77% smaller. These are not whole-application database sizes.
About the storage update
DuckDB is a column-oriented database designed for analytical queries. On new installs and after conversion, it stores and aggregates HardwareVisualizer history, including records used by Cooling Insight. It does not require a separate database server.
Measured on September 27, 2026, using synthetic Process Stats and Ambient histories (stable cases, 15 process samples per minute). The table shows the median DuckDB file size across 3 independent builds; observed ranges: 30 days 16.9–17.1MiB; 90 days 50.1–50.2MiB; 1 year 202.5–202.8MiB. File sizes were measured after closing and checkpointing: SQLite includes indexes; DuckDB includes metadata and WAL, with no explicit indexes or primary-key constraints in this fixture. Environment: macOS 26.6.2; SQLite 3.46.0 / DuckDB 1.5.5. This reruns the historical engine experiment; it does not measure final application storage or migration overhead.