![]() ![]() Toggle whether delta compression is enabled when sending packages to targets. In Octopus, we added the system variable settings:Ĭontrols the number of package acquisitions that will be allowed to run concurrently. Please help or provide information on how we can get this better. The performance we have right now is not acceptable. I am asking both Inedo and Octopus Deploy for help with this. However, in Octopus, we can "test" the external feed by submitting a package name, and it will return the available version. 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). Is there something we need to do to get better performance overall? ![]() Is there something we need to do to get more caching setup? Now we seem to get 4 or more, and the time to acquire is getting shorter, as if there is some caching going on. ![]() At first, we couldn't do 3 or more packages before it failed. Note, that over time, we're seeing some improvement. If I test using 2 packages, it takes 120 seconds. ![]() Testing with a single package from the ProGet server, it takes Octopus 10-15 seconds to acquire the package. 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. Using TeamCity to build the NuGet packages, we have no problem in getting these on the ProGet server. Our next phase is to implement more secure package server and ProGet was chosen. These were kept on a simple file server (nothing special). We've only recently started using Octopus Deploy. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |