search

bufferoverflow / verdaccio-gitlab

private npm registry (Verdaccio) using gitlab-ce as authentication and authorization provider
MIT License
161 stars 56 forks source link

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

Open dejan9393 opened 3 years ago

dejan9393 commented 3 years ago

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