Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MongoDB: remove results w/o covered index scan #64

Merged
merged 1 commit into from
Apr 7, 2025
Merged

MongoDB: remove results w/o covered index scan #64

merged 1 commit into from
Apr 7, 2025

Conversation

rschu1ze
Copy link
Member

@rschu1ze rschu1ze commented Apr 7, 2025

Reasons:

  • covered index scans are strictly better than brute-force scans
  • also, covered index scans are recommended by MongoDB's tuning best practices
  • A full MongoDB benchmark run runs multiple days on my test machine, reducing the variability in the benchmark helps with reproducing new results
  • All links in the original blog post to results without covered index scans continue to work

@rschu1ze rschu1ze merged commit 25608e3 into main Apr 7, 2025
@rschu1ze rschu1ze mentioned this pull request Apr 7, 2025
Merged
rschu1ze added a commit that referenced this pull request Apr 8, 2025
@rschu1ze
Remove Postgres pglz
41128e3 
This serves a similar purpose as #64.

Reasons:
- The measurements for Postgres take ages already, this will help to
  reproduce results more easily.
- lz4 is strictly better than pglz in ClickBench, Google will find you
  various blog posts which confirm this
- All links in the [original blog
  post](https://clickhouse.com/blog/json-bench-clickhouse-vs-mongodb-elasticsearch-duckdb-postgresql)
  to pglz results will continue to work.
@rschu1ze rschu1ze mentioned this pull request Apr 8, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@rschu1ze