fix: change all HASH indexes to BTREE to optimize writes #1825
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Vercel deployment URL: https://stacks-blockchain-76kamf52i-blockstack.vercel.app 🚀 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## beta #1825 +/- ##
=======================================
Coverage 71.71% 71.72%
=======================================
Files 91 91
Lines 11835 11835
Branches 2622 2622
=======================================
+ Hits 8488 8489 +1
+ Misses 3194 3193 -1
Partials 153 153 ☔ View full report in Codecov by Sentry. |
zone117x
approved these changes
Jan 12, 2024
blockstack-devops
pushed a commit
that referenced
this pull request
Jan 12, 2024
## [7.8.0-beta.3](v7.8.0-beta.2...v7.8.0-beta.3) (2024-01-12) ### Bug Fixes * change all HASH indexes to BTREE to optimize writes ([#1825](#1825)) ([234936b](234936b))
|
🎉 This PR is included in version 7.8.0-beta.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
blockstack-devops
pushed a commit
that referenced
this pull request
Jan 23, 2024
## [7.8.0](v7.7.2...v7.8.0) (2024-01-23) ### Features * add `/extended/v2/smart-contracts/status` endpoint ([#1833](#1833)) ([3535c11](3535c11)) * run inserts in batch and in parallel when processing new block ([#1818](#1818)) ([86dfdb5](86dfdb5)) * upgrade to node 20, use bookworm-slim image ([#1832](#1832)) ([0a42109](0a42109)) ### Bug Fixes * change all HASH indexes to BTREE to optimize writes ([#1825](#1825)) ([234936b](234936b)) * log block event counts after processing ([#1820](#1820)) ([9c39743](9c39743)), closes [#1819](#1819) [#1819](#1819) * optimize re-org queries and indexes ([#1821](#1821)) ([5505d35](5505d35)) * parallelize re-org update queries ([#1835](#1835)) ([340a304](340a304))
|
🎉 This PR is included in version 7.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our HASH indexes did not have enough cardinality, i.e. there were a lot of collisions which forced postgres to create "secondary" indexes of data inside each of those collisions. Changing indexes to BTREE helped reduce write latency tremendously (from ~5-10 seconds per block to ~150-900ms per block.