satis icon indicating copy to clipboard operation
satis copied to clipboard

Gitlab + Satis, "Scanning packages" takes a long time

Open rask opened this issue 8 years ago • 4 comments

Our company has uses Bitbucket and Gitlab for repo hosting.

Packages that are in Bitbucket are fetched quite fast, in 10 seconds usually. Now we introduced a package that sits at Gitlab.com. Not "Scanning for packages" takes more than 2 minutes at minimum.

Any ideas why this is? Let me know how to debug this properly so we can see if this is something with Satis or the server configuration where Satis is being run in.

The packages are regular Composer packages.

In essence this is the same issue as the closed #315. Could it be related to the API metadata fetch that differs between Gitlab and Bitbucket?

rask avatar May 02 '17 11:05 rask

Not sure. Is the delay significant on every run? Or only the first run? (I.e. does caching help or not?)

Would help if you could provide a verbose output log.

alcohol avatar May 02 '17 11:05 alcohol

We run into the same issue. When running the command with -vvv, I can't see anything out of the ordinary, yet it takes nearly 3 minutes to complete the task for just 5 repositories.

It's not a deal break for us, but it does feel like there may be some underlying issue that causes this.

Jacco-V avatar Jun 04 '17 14:06 Jacco-V

Ran into the same issue with Satis & GitLab, loads very slowly.

mbardelmeijer avatar Jun 06 '17 19:06 mbardelmeijer

Can be related: https://gitlab.com/gitlab-org/gitlab/-/issues/227698

igronus avatar Sep 14 '23 13:09 igronus