-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
perf: Graphql CDN using Stellate #7623
Conversation
…ck.stellate.sh' * fix(constants.ts): update stick indexer endpoint to 'https://query-stick.stellate.sh'
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
AI-Generated Summary: This pull request includes changes to two files: |
Reviewpad Report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does it work? does it only cache data?
Will we need it for all indexers? wouldn't we have a problem on the billing?
Do you have acces at some sort of backend dashboard?
It wraps the subsquid endpoint with stellate
for testing maybe we can test with one endpoint first? they have a free plan with unlimited requests. the limitation is only working on 2 endpoints, and need to put their badge
I just created the account by myself. what we need only subsquid endpoint to use stellate |
Caching graphql is a good idea, but I also have some concerns.
|
we can use custom header to bypass the cache https://stellate.co/docs/graphql-edge-cache/bypass-the-cache or, not putting all Types in the cache. currently in the rules I put [
'NFTEntity',
'NFTEntitiesConnection',
'CollectionEntity',
'CollectionEntitiesConnection',
'Event',
'EventEntity',
'LastEventEntity',
]
interesting, do we need unfortunately, we need to adjust the subscription over HTTP instead of WS |
Ah GraphCDN => Stellate? We've been considering this one in the past. |
…ss://squid.subsquid.io/stick/graphql' as the WebSocket URL
For the subscription query, what if we fallback to the subsquid endpoint? like this c01503c
yes, cdn for graphql |
So looking forward to hear opinion from @kodadot/internal-dev about using stellate.
We can fallback to the sqd endpoint. But I would be happy to try it on AssetHubs (2 endpoints) and if we would see potential benefit we can scale from there. |
meh.. I have no opinion
yes we could try that first |
* fix(TheFooter.vue): add missing import for useTheme * refactor(TheFooter.vue): remove unused import for TranslateResult
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Code Climate has analyzed commit e792f52 and detected 0 issues on this pull request. View more on Code Climate. |
lets try it then? @vikiival |
Shouldn't be the badge in the readme? |
Thanks! |
😍 Perfect, I’ve sent the payout 🪅 Let’s grab another issue and get rewarded! |
looking for improvement. |
It is probably not significant since I only set the cache to 60 seconds |
90% of landing 🥹 |
aahh, I see. let me check |
feel free to test on #7725 |
checking 👍 |
confirmed, with SSR from #7725 looks better FCP from 9xx ms -> 6xx ms this will help us to increase the scores |
Hi @kodadot/internal-dev. Would you like to try Stellate for our GraphQL endpoint? In a simple comparison, it appears to be faster. This could help us if we get a large number of visitors at the same time. Perhaps if the number of visitors is not too high, the effect might not be too noticeable. For now, I’ve set the cache on this endpoint to last for 60 seconds.
https://stellate.co/docs/graphql-edge-cache/cache-rules
PR Type
Context
Had issue bounty label?
Copilot Summary
🤖 Generated by Copilot at 45af347
This pull request adds support for the new Stellate indexers, which are a different kind of Subsquid indexer for the NFT gallery. It updates the
indexers.ts
andconstants.ts
files to handle both Stellate and Squid indexers and use the appropriate one for each network.🤖 Generated by Copilot at 45af347