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

GitLab API results are not cached, causes high CPU usage on GitLab server #125

Open
dejan9393 opened this issue Mar 10, 2021 · 0 comments · May be fixed by #126
Open

GitLab API results are not cached, causes high CPU usage on GitLab server #125

dejan9393 opened this issue Mar 10, 2021 · 0 comments · May be fixed by #126

Comments

@dejan9393
Copy link

I've run into an issue where my private GitLab instance is flooded by requests from verdaccio GitLab, forcing 6 cores to all run at 100% capacity due to the puma workers in GitLab.

The promises for the GitLab API calls for GitlabAPI.users.current(), GitlabAPI.Groups.all, and GitlabAPI.Projects.all could be cached to avoid spamming the GitLab API with multiple similar requests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Cache GitLab responses to avoid spamming the GitLab server communitybuilders/verdaccio-gitlab
1 participant
@dejan9393