Subgraph is out of sync

[JohannesHoppe]

Subgraph at https://api.bscgraph.org/subgraphs/name/cakeswap is unusable because it's absolutely out of sync.

see https://twitter.com/PancakeSwap/status/1362428932545372163

[ffarhanaamin]

Is there any update on the issue? I

[JohannesHoppe]

They don't care. https://pancakeswap.info/ is broken for ages, too.

[JohannesHoppe]

FYI @ChefKai

see also pancakeswap/pancake-info-v1#26

[ffarhanaamin]

i don't see any responses? I don't think they are ever going to fix this.

[ChefKai]

Hello,

A bit of history here, when PancakeSwap was started, there was no support for subgraph on Binance Smart Chain; so we had to use the open-source package provided by Graph Protocol to run our own archive nodes and subgraphs.
Following our expansion, the subgraphs started to be falling behind (end of January/start of February), and we reached out to TheGraph to start tinkering with Binance Smart Chain and integrate it on their hosted service (that also opened doors for other projects/users to deploy their own subgraphs 🎉 ). Despite our best efforts, you can see that after deploying 18 days ago, it still far from behind synced; same status as the one on our infrastructure deployed few weeks earlier (cakeswap, the one currently being used on .info), even though we have optimized/removed a few extra operations when processing events to speed up the process. Also, you can check in the Logs tab, the runtime each function in order to process the data; most of the time it is below 30ms.

Blog: https://www.binance.org/en/blog/the-graph-brings-indexing-and-querying-to-binance-smart-chain/
TheGraph: https://thegraph.com/explorer/subgraph/pancakeswap/exchange

Ultimately, we will have to remove some features on this subgraph to keep it lightweight in order to keep-up with the block time + events; or use a 3rd-party data provider such as BitQuery.

[JohannesHoppe]

Hello @ChefKai. Many thanks for you reply and please excuse my frustration. 😄

You might want to take a look at https://github.com/sushiswap/sushiswap-subgraph. They have splitted the big subgraph into smaller pieces, to improve the performance.

[gotjoshua]

Ultimately, we will have to remove some features on this subgraph to keep it lightweight in order to keep-up with the block time + events; or use a 3rd-party data provider such as BitQuery.

any ETA on this?
maybe the team could close these various issues with circular refs, and open one with a clear strategy and eta...