You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2023. It is now read-only.
After each query, we collect information about its rows read and rows written, and use it to bump our global metrics. We should also consider extending our protocol so that we return those values to the user as well. That would help users optimize queries, since they'd be able to compare which queries cost how many units.
That would make responses larger though, so it can affect throughput, esp. for small responses, so perhaps this mode should be opt-in, used only for query planning and debugging.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After each query, we collect information about its rows read and rows written, and use it to bump our global metrics. We should also consider extending our protocol so that we return those values to the user as well. That would help users optimize queries, since they'd be able to compare which queries cost how many units.
That would make responses larger though, so it can affect throughput, esp. for small responses, so perhaps this mode should be opt-in, used only for query planning and debugging.
The text was updated successfully, but these errors were encountered: