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

Add metrics for current cache/object readers #5202

Closed
wants to merge 1 commit into from

Conversation

polyrabbit
Copy link
Contributor

Align with object_request_uploading, so we know the pressure we are exposing to the backend storage.

Signed-off-by: Changxin Miao <miaochangxin@step.ai>
Help: "number of storage readers",
ConstLabels: prometheus.Labels{"storage": "object"},
}, func() float64 {
return float64(store.objectReaders.Load())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can add a limit for concurrent GET, and know the actual concurrency using that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently we don't have that limitation right?

Help: "number of storage readers",
ConstLabels: prometheus.Labels{"storage": "cache"},
}, func() float64 {
return float64(store.cacheReaders.Load())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can know the concurrent IO from dcState

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

concurrency counter is only updated in unstableDC implementation. To track concurrency in other states, I have to move it to baseDC?

@davies
Copy link
Contributor

davies commented Sep 30, 2024

We usually use the rate of object_request_durations_histogram_seconds as the metric of concurrency, no new metric needed.

Same to other operations or requests.

@polyrabbit
Copy link
Contributor Author

OK, closing

@polyrabbit polyrabbit closed this Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants