Skip to content

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

New issue
New issue
Open
#126
Open
GitLab API results are not cached, causes high CPU usage on GitLab server#125
#126
@dejan9393

Description

@dejan9393
dejan9393
opened on Mar 10, 2021

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

Activity

dejan9393
linked a pull request that will close this issue on Mar 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      GitLab API results are not cached, causes high CPU usage on GitLab server · Issue #125 · bufferoverflow/verdaccio-gitlab