Deployments are slow

(ge.bai) #1

Hello,

After upgrading Octopus to v2019.5.7, we found that deployments are slow from time to time.

Same deployment to the same host takes 10 seconds the first time and can take 15 minutes the second time.

We do not see obvious cause from the log.

Any suggestions will be appreciated!

Ge

Attached two screenshots of log:

It’s not clear to me that why there is a 4 mins gap in the acquire packages step.
13:39:07 - 13:43.17

This step took only 1 second in the earlier deployment (same project, same deployment, and same host)

Other steps are slow too, but I am just using the first step as an example.

(Paul) #5

We also noticed this on v2019.5.7 - Acquiring packages can be as quick as it was before (seconds) or take many minutes. Its fairly intermittent but noticeable.

Apologies for not providing any server logs relating to this; i came here to post about a different issue and noticed this.

Have since upgraded to v2019.5.10, lets see how it goes.

(Daniel Fischer) #6

Hi,

It looks like we have some news regarding this issue.

We are fairly confident that the issue relates to the way in which Octopus server is establishing connections to Tentacles associated with the deployment. Typically, these connections should happen in parallel, however it looks like they are currently happening sequentially. This can cause some serious delays if there are machines which Octopus cannot establish a connection with during the deployment.

The following GitHub Issue has a more detailed explanation of this issue and will have updates on the release for the fix.

Currently this is affecting Octopus version 2019.5.2 - 2019.5.10 (Inclusive). We have a fix planned for the 2019.5.11 release which we will hopefully release today or tomorrow.

The current workaround outside of upgrading to 2019.5.11 when it is released is to downgrade your Octopus server version to an unaffected version.

Alternatively, if you take action to ensure that Octopus can quickly connect to all machines, this issue should not be encountered. This could mean deleting any inaccessible machines.

The best option here would be to upgrade to our latest version of Octopus Server 2019.5.11 when it is released.

If after the upgrade to 2019.5.11 and are still encountering performance issues, please let us know.

Let me know if you have any questions or thoughts here.

Best regards,
Daniel

(ge.bai) #7

Thanks, Daniel!