Disk I/O is overloaded on Gitlab after enabling and configuring Jigit

[Former user]

Hello Dmitrii,

First of all, your plugin is really awesome, and best of all is that it's free :D

However, I have a problem after enabling Jigit and configuring about 25 repositories (relatively small repos, ~ 4000 total commits of all repos): My Gitlab server is showing high level CPU usage, specifically I/O operations. Before I'have been enabled Jigit the CPU usage was normal, so less as you can see on the image below. It was enough to disable Jigit and everything returned to normal.

I followed your tips that are on the Wiki to try reduce this high usage, but it didn't work. Unfortunately it is preventing me to use my Gitlab server with Jigit, because it gets very slow while Jigit is enabled.

Question: Is this behaviour normal for this number of repositories/commits? Is there any adjust I can do to solve this issue?

I am counting on your help.

Thank you!

[Dmitrii Apanasevich]

Hi,

It looks a bit weird. Have you configured your repositories with "index all branches" or not?

If Jigit indexes only master branches, then for 4Kcommits it'll produce about 9K GitLab API calls at maximum. It doesn't look like enormous load.

Try to disable all repositories except one of them with small number of commits, enable "index specific branches" option and look at LA.

[jhonatanmorais]

Hi,

After your tips, I've tried enabling all repositories again and I've been disabling one by one to identify where was the problem. This way I was able to identify that some repositories (3 ~ 4) were causing this problem. That repositories were migrated from SVN to Gitlab, each one has about 3k commits and I didn't notice it before, because Jigit has showed just 4 commits of each one, even many hours after that they were configurated and activated (more than a day). I could not figure out the real reason this was happening, but how that projects aren't so important to me (just historical repositories for consultation) I'm gonna leave that repositories out off Jigit.

Thank you so much for your feedback!

[Dmitrii Apanasevich]

You are welcome!

That repositories were migrated from SVN to Gitlab, each one has about 3k commits and I didn't notice it before, because Jigit has showed just 4 commits of each one, even many hours after that they were configurated and activated (more than a day). I could not figure out the real reason this was happening

Maybe, these repositories contain large commits, and GitLab tried to calculate diffs for these commits during Jigit calls. And Jigit couldn't get them from GitLab, and that is why it showed only 4 commits for them.

Ultimately, the main result is that you can use Jigit.

I'll be grateful if you leave a review here. Reviews help other potential users to understand whether plugin is useful or not.