-
Notifications
You must be signed in to change notification settings - Fork 48
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
SLO1 performance issues #1954
Comments
Related to the research currently being worked on. |
Recently several improvements regarding this were implemented: storing the package configuration in DB, not running private repo check for result events and optimizing getting the PR info via API; so let's see how the situation will improve. If needed, we can implement also #1923 . |
After this fix the number of events taking more than 15s before giving a feedback has lowered, still we have some of them in a day. An issue is already being tracked here There is another recurring issue which I am not sure we could resolve.
After I think this time is needed for cloning the project. Probably we should really avoid logging events taking less than 25/30s if half of this time is needed to clone (?) the project locally? The latests exceptions I examined have taken the listed time for the listed repos... |
We are having SLO1 error budget issues.
These are mostly caused by db performance issues and we are working on them:
We are also planning further improvements:
The text was updated successfully, but these errors were encountered: