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

Session metrics for cost #2756

Closed
Tracked by #2718
BohuTANG opened this issue Nov 12, 2021 · 3 comments
Closed
Tracked by #2718

Session metrics for cost #2756

BohuTANG opened this issue Nov 12, 2021 · 3 comments
Labels
A-query Area: databend query

Comments

@BohuTANG
Copy link
Member

BohuTANG commented Nov 12, 2021

Summary

To measure a cost of a query, there are many metrics need addressed:

  1. Binding tenant_id and cluster_id to session for identifiy who own the session.
  2. Binding a tokio runtime to session for memory usage and cpu limited.
  3. Binding read_bytes/write_bytes/execution_time to the session for the last query

The struct of the Session need refactored for the fine-grained resource managing.

@ZhiHanZ
Copy link
Collaborator

ZhiHanZ commented Nov 12, 2021

we should also stat on request per sec, io( disk + s3) and label them all with tenant and cluster_name

@BohuTANG
Copy link
Member Author

we should also stat on request per sec, io( disk + s3) and label them all with tenant and cluster_name

Sure, the k8s layer should provide a cost model? like: https://github.com/kubecost/cost-model/blob/develop/kubecost-exporter.md

@ZhiHanZ
Copy link
Collaborator

ZhiHanZ commented Nov 13, 2021

we should also stat on request per sec, io( disk + s3) and label them all with tenant and cluster_name

Sure, the k8s layer should provide a cost model? like: https://github.com/kubecost/cost-model/blob/develop/kubecost-exporter.md

need to investigate on possible integration with the cost model

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-query Area: databend query
Projects
None yet
Development

No branches or pull requests

2 participants