-
Notifications
You must be signed in to change notification settings - Fork 111
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.
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
SPIKE: Investigate block time ingestion #1715
Comments
The spike is caused by the It doesn't look like the materialized view sql can be sufficiently optimized. We likely need to move to an approach of tracking nft custody more explicitly. Relevant code here: stacks-blockchain-api/src/datastore/pg-write-store.ts Lines 3000 to 3026 in b95eac7
stacks-blockchain-api/migrations/1636130197558_nft_custody.js Lines 3 to 22 in b95eac7
|
Block ingestion is taking either ~3.5 second or around 30 seconds, roughly evenly distributed over time. The slow 30 second ingestion time is going to be an issue with the 5 second Nakamoto blocks.
There isn't much deviation from these two durations, which implies there should be a relatively straightforward cause. The first thing that comes to mind is that re-orgs may trigger the 30 second blocks.
More debugging is needed to confirm the cause and look into a fix.
The text was updated successfully, but these errors were encountered: