Buildmaster slow to deploy to environments

Whenever I push a build to a new environment it will regularly take 2+ minutes before it ever starts running the first step (Deploy artifact) and looks like the screenshot below. What is causing this slowness? The build server and the server it's deploying to are both on the same internal network with a very fast connection between them. Our staging environment is using the SOAP agent and our production is using the TCP agent but both are equally slow.

Is there anything I can do to speed it up?

Slow Deploy

Product: BuildMaster
Version: 4.2.6

This sounds like it was caused by issue BM-1486 which was resolved in 4.2.7, if you upgrade to the newest 4.2 version (4.2.8) it should resolve the issue.

Just updated to 4.2.8 and did a new build and I see the exact same behavior.

Are you able to run the service interactively before executing a deployment to see if there any additional log messages that are output to the console window?

Just did what you suggested, while the deploy is spinning for the 2 minutes or so all that is groups of:

Executing PlanActionExecuter..
Getting executions to execute...
No executions found
PlanActionExecuter executed

Over and over again.

Then when the build finally picks up and does the deploy I saw:

[Exec #2825] Getting next action...
Initializing server 6...
Server 6 initialized
[Exec #2825] Executing PlanAction #5484

And then a bunch more exec steps.

If you go to Admin->All Settings, what is the value for PlanExecuterThrottle (in the Service section)?

The PlanExecuterThrottle is set to 5 seconds

Any more ideas?

Thanks for your time looking into this issue.

Would you be able to upgrade to the recently-released v4.3? This version has essentially completely rewritten the execution engine (to support things like parallelism, iterating servers/deployables, etc.), so it may just fix whatever problem was inherit in the pre-4.2 line.

Make sure to read the upgrade notes before upgrading.

Just upgraded to Version 4.3.2 (Build 3)

Still getting 2+ minute pauses before the deploy starts though.

Can I reach you directly somehow?

Yes, drop us a line at support-at-inedo-dot-com.

It sounds like the issue is happening in server prep stage.

Just to follow up, got some help from the inedo folks and we discovered that the server hosting the sql server database had its system clock slightly off which was causing the delay till the start of execution.