The Graph is a web3 protocol for organizing and accessing blockchain data 🧑‍🚀 Official account of The Graph ecosystem 🌐
thegraph.com

Are you building subgraphs on @graphprotocol?   

Here are 2 simple tips to boost your subgraph's indexing and querying performance 🔥

A small thread 🧵

1. Mark entities as immutable whenever possible If you will not edit the entity in the future.

In schema.graphql, you can mark entities as immutable as given below.

2. Use type Bytes for id in entities rather than type ID

How does it make a difference?
In simple words, type ID takes twice the space of Bytes and comparison of strings in Bytes is much cheaper than in type ID.

This performance measurement was done in a controlled environment where 4 subgraphs were deployed.

base - immutable ❌ & bytes ❌
immutable - immutable ✅ & bytes ❌
bytes - immutable ❌ & bytes ✅
both - immutable ✅ & bytes ✅

These 2 tips are very small changes, but they will greatly impact the subgraph's indexing and querying performance.

Do check the detailed blog by David Lutterkort

These 2 tips are very small changes, but they will greatly impact the subgraph's indexing and querying performance.

Do check the detailed blog by David Lutterkort

https://thegraph.com/blog/two-simple-subgraph-performance-improvements/

If you have any more queries, feel free to hop on our discord channel.

If you have any more queries, feel free to hop on our discord channel.

https://discord.gg/graphprotocol

How does it make a difference?

When entity types are marked as immutable, 
graph-node uses database indexes that are much cheaper to build and maintain than mutable entities.