Optimize `store_get_asc_new`

Open
#3,874 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
backend, performance

Research direction

Start by locating the store_get_asc_new entry point and reproduce its CPU cost locally using the listed subgraphs as workload examples. Benchmark the current behavior before investigating optimization opportunities; done means the operation remains correct and shows a measurable CPU improvement.

Written by the indexing model from the issue text.

Description

area/runtime good first issue performance Stale

This shows as a major time consumer in a few subgraphs including:
https://thegraph.com/hosted-service/subgraph/sushi-labs/users-polygon (Qma5YzDtseXGJfwt1dGMmRwMaqvbgdSgnprWSdnp5gQf3n)
https://thegraph.com/hosted-service/subgraph/sushi-labs/users-ethereum (QmV4tr3xCx21z77YhPNLM7dJJtGmQ7tvzKpLJTBHNrBd5B)
https://thegraph.com/hosted-service/subgraph/sushiswap/sushiswap-polygon (QmT3h6RJvw5zJ6Gq6v6xt1sNExxHcUXEXc4y9rGHjYmPFj)

Since this is purely a CPU operation it should be possible to benchmark it locally and hopefully make significant optimizations.

Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphprotocol/graph-node

All issues in graphprotocol/graph-node

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.