Skip to content

q2 on TimescaleDB is 5 ms, not about 2 #384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdatcmd merged 1 commit into from
Aug 4, 2026
Merged

q2 on TimescaleDB is 5 ms, not about 2 #384

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/benchmarks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -489,7 +489,7 @@ Rows Removed by Filter: 99995680
It reads all 667 row groups and filters 99,995,680 rows to return 4,320. The zone maps cannot help,
because neither key is sorted in the stored order. Every stripe holds all 4,000 hosts.
The minimum and maximum `hostname` of each group therefore covers the whole set.
TimescaleDB answers the same query in about 2 milliseconds. It excludes all but one
TimescaleDB answers the same query in 5 milliseconds. It excludes all but one
chunk on time, then reads one `hostname` segment through an index.

**So this table measures pgColumnar in the layout that suits it least.** A user with
Expand Down
Loading