Supporting methodology and editorial history

Article: Half the wait: 8DB time-series loading vs. QuestDB on an M1 laptop

Retained October 9, 2026 from the article at source c04aea4. These passages preserve the original scope, methodology and revision history behind the commercial summary. They are not new test results. Original source references remain in the article.

The report describes exact counts and selected host-level minimum, maximum and average checks, with an additional sum check for QuestDB. That is meaningful validation within the harness’s scope. It does not establish that every possible query was tested.

The September timings suggest a comparative hypothesis worth testing: 8DB's shorter loading interval could reduce energy relative to QuestDB. The calculation depends on their average whole-system power. At equal average power, the recorded times imply about 50% less loading-interval energy; at 1.5 times QuestDB's average power, about 26% less. At approximately 2.02 times its power, that modeled advantage disappears.[9] We have not measured which of these conditions applies.

A second campaign on April 14 retained ten invocation means for the same named ten-million-entry benchmark. The mean of the corresponding rates was 60.092 million entries per second, approximately 2% below the April 7 mean.[4] These campaigns provide a historical reference for the component measurement. Without a matched competitor construction test, they do not establish its competitive standing; the difference between dates also does not isolate a software regression.