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.

Sign up for GitHub

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

Jump to bottom

Determine WMStats current limits #11571

Closed
khurtado opened this issue Apr 21, 2023 · 2 comments · Fixed by #11885 or #11924 · May be fixed by #11907
Closed

Determine WMStats current limits #11571

khurtado opened this issue Apr 21, 2023 · 2 comments · Fixed by #11885 or #11924 · May be fixed by #11907
Assignees
@amaltaro
Labels
R&D WMStats

Comments

@khurtado
Copy link
Contributor

Impact of the new feature
WM in general

Is your feature request related to a problem? Please describe.
This issue is part of #11408

Describe the solution you'd like
Quantify the limits of WMStats related to CouchDB load, features used that could be reduced change to extend some limits (e.g.: job failure records), number of workflows in the system, WQEs, etc.

Describe alternatives you've considered
None

Additional context
None
@khurtado khurtado converted this from a draft issue Apr 21, 2023
@amaltaro amaltaro added the R&D label Apr 21, 2023
@amaltaro amaltaro mentioned this issue May 5, 2023
Open
5 tasks
@amaltaro amaltaro self-assigned this Oct 25, 2023
@amaltaro amaltaro moved this from Todo to In Progress in WMCore quarterly developments Oct 25, 2023
@amaltaro
Copy link
Contributor

amaltaro commented Jan 8, 2024

In addition to evaluating the limits of the service, I think it's also important to characterize how wmstatsserver is currently used.
The CMSWEB monitoring required changes and those have been deployed in production today, see:
https://its.cern.ch/jira/browse/CMSKUBERNETES-253

Now we can see which REST APIs are accessed, how often, time to serve them, etc.

@amaltaro amaltaro mentioned this issue Feb 3, 2024
Merged
@amaltaro amaltaro mentioned this issue Feb 20, 2024
Open
@amaltaro amaltaro mentioned this issue Mar 7, 2024
Merged
@github-project-automation github-project-automation bot moved this from In Progress to Done in WMCore quarterly developments Mar 7, 2024
@amaltaro
Copy link
Contributor

amaltaro commented Mar 7, 2024 •
edited
Loading

Not yet the moment to close this issue out.

I will start providing a summary here of findings, documents, fixes and so on:

@amaltaro amaltaro reopened this Mar 7, 2024
@amaltaro amaltaro moved this from Done to In Progress in WMCore quarterly developments Mar 7, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in WMCore quarterly developments Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amaltaro amaltaro

Labels
R&D WMStats
Projects
WMCore quarterly developments
Status: Done
Milestone
No milestone
2 participants
@amaltaro @khurtado