We're new to ProGet. We've only recently started using Octopus Deploy. One project has 43 NuGet packages. These were kept on a simple file server (nothing special). Our next phase is to implement more secure package server and ProGet was chosen.
Using TeamCity to build the NuGet packages, we have no problem in getting these on the ProGet server.
However, Octopus Deploy experiences severe delays when trying to deploy multiple packages, to the point where the Octopus component on the target server (the Tentacle) times out and terminates the connection, resulting in a deployment failure.
Testing with a single package from the ProGet server, it takes Octopus 10-15 seconds to acquire the package. If I test using 2 packages, it takes 120 seconds.
Note, that over time, we're seeing some improvement. At first, we couldn't do 3 or more packages before it failed. Now we seem to get 4 or more, and the time to acquire is getting shorter, as if there is some caching going on.
Is there something we need to do to get more caching setup?
is there something we need to do to get better performance overall?
Note: I can do a simple SQL script and interrogate the database in a split second to find the package (but that's not downloading it). However, in Octopus, we can "test" the external feed by submitting a package name, and it will return the available version. this takes 10-15 seconds.
I am asking both Inedo and Octopus Deploy for help with this.
the performance we have right now is not acceptable. Please help or provide information on how we can get this better.