-
Notifications
You must be signed in to change notification settings - Fork 189
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.
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
performance problems with RubyGems and Artifactory #337
Comments
I think this is the same problem being worked on at rubygems/rubygems#6632? |
I think you might be right. I'll see if the PR fixes this issue on my side with a patch. |
I don't think there is any way to patch this because of when it is loaded, so I'm waiting for the fix version I guess. |
we are tracking this through the Artifactory side issue: https://jfrog.atlassian.net/browse/RTFACT-13635 |
Hey, just came across this. This is fixed in rubygems. Are you seeing the improvement? |
I'm pretty sure this was indeed fixed, let's close! @coldnebo if you're still seeing issues please open a separate issue at https://github.com/rubygems/rubygems. |
we are seeing a massive performance hit when trying to do a bundle install where the source is an Artifactory based repository.
For a Gemfile where one gem changed some minor versions, 'bundle install' recalculation took about 5 seconds. Now it takes 11 minutes.
#292 seems like an explanation from Artifactory's side, but rubygems discounts this as a documentation issue for the compact API.
However, the compact API should be invoked by the latest version of bundler (2.4.13 at this writing) but apparently isn't. Instead two fallback apis are called resulting in 404s, which then trigger the third fallback requesting gemspecs for all gem versions (which takes about 11 minutes on my system).
This is an unacceptable change in performance that seems related to the changes rolled out in the compact API. We are urgently searching for solutions or workarounds to this issue.
references
how the issue presents
artifactory/api/gems/gems-repos/versions
fails with a 404.artifactory/api/gems/gems-repos/api/v1/dependencies
fails with a 404.environment
The text was updated successfully, but these errors were encountered: