Skip to content
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

RFC: Give visibility into the cost of an operation #37

Open
JoviDeCroock opened this issue Dec 2, 2023 · 0 comments
Open

RFC: Give visibility into the cost of an operation #37

JoviDeCroock opened this issue Dec 2, 2023 · 0 comments
Labels
RFC A discussion about a future feature

Comments

@JoviDeCroock
Copy link
Contributor

Summary

In fuse we already optimise a lot by going for dataloader,... however it's still hard to observe the potential cost of an operation. We should work on getting insights for this.

Proposed Solution

There are a number of ways to tackle this, we could generate a file that has all the paths of a given operation and cross-reference that in development to how long the server takes to resolve all of that.

We could leverage complexity scoring to have a base heuristic for query-cost.

We could leverage grafast under the hood, grafast already has a base concept of query-plans which makes it easier to reason about query-cost. We own the server-layer so there's a good chance that we can hide the complexity of grafast for the consumer of the library but give them the performance benefits.

@JoviDeCroock JoviDeCroock added the RFC A discussion about a future feature label Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC A discussion about a future feature
Projects
None yet
Development

No branches or pull requests

1 participant