graphprotocol / graphprotocol/graph-node
[Bug] Subgraph indexing very slow when block handler is used even if block handler's start block has not reached
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Bug report
When this subgraph is deployed with block handler, subgraph is indexing very slow even if block handler's start block has not reached. When the data source with block handler is removed, subgraph is syncing much faster.
Deployment ID without block handler - QmaTYtcFZUobuUqdZL8mjvMhYUD5qE9egsMJQHsJkpMV3z
Deployment ID with block handler - QmQBNYbUVLvLVYEtc7zRRWJNMwkETVfn73VT2z2c7eden4
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the indexing behavior of deployment QmaTYtcFZUobuUqdZL8mjvMhYUD5qE9egsMJQHsJkpMV3z without a block handler with QmQBNYbUVLvLVYEtc7zRRWJNMwkETVfn73VT2z2c7eden4 with one. Trace how block-handler data sources are processed before their configured start block, then verify that indexing speed is unaffected until that block is reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, rust
- Domain
- backend, blockchain, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100