Self Hosted Devops Agent Limits

%3CLINGO-SUB%20id%3D%22lingo-sub-3114272%22%20slang%3D%22en-US%22%3ESelf%20Hosted%20Devops%20Agent%20Limits%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3114272%22%20slang%3D%22en-US%22%3E%3CP%3ERecently%20one%20of%20my%20developer%20reached%20out%20to%20me%20to%20find%20a%20way%20to%20speed%20up%20a%20software%20deployment%20we%20do%20once%20a%20week.%26nbsp%3B%20This%20deployment%20hits%203%20servers%20in%20our%20self%20hosted%20environment%3A%20a%20large%20SQL%20server%2C%20and%202%20front%20end%20servers.%26nbsp%3B%20The%20deployment%20pipeline%20goes%20through%20about%2050%2B%20parallel%20stages%20on%20the%20SQL%20server%20so%20we%20had%2012%20agents%20on%20the%20SQL%20server.%26nbsp%3B%20The%20SQL%20server%20has%2016%20cores%20currently.%26nbsp%3B%20Last%20week%20I%20increased%20it%20to%2015%20agents%20and%20we%20saw%20about%2012%25%20improvement%20in%20speed%20to%20complete%20the%20pipeline.%26nbsp%3B%20We%20are%20still%20seeing%20the%20lack%20of%20agents%20being%20the%20major%20bottleneck%20here%20and%20are%20looking%20to%20add%20more%20but%20we%20are%20concerned%20that%20going%20over%201%20agent%20per%20core%20will%20likely%20make%20it%20slower%20or%20cause%20problems%20with%20the%20deployment.%26nbsp%3B%20The%20only%20documentation%20I%20have%20found%20that%20mentions%20a%20core%20to%20agent%20count%20is%2024%20cores%20and%204%20agents%20on%20non%20hosted%20devops.%26nbsp%3B%20I%20reached%20out%20to%20MS%20support%20and%20they%20pointed%20me%20here%20as%20this%20is%20not%20break%20fix.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Recently one of my developer reached out to me to find a way to speed up a software deployment we do once a week.  This deployment hits 3 servers in our self hosted environment: a large SQL server, and 2 front end servers.  The deployment pipeline goes through about 50+ parallel stages on the SQL server so we had 12 agents on the SQL server.  The SQL server has 16 cores currently.  Last week I increased it to 15 agents and we saw about 12% improvement in speed to complete the pipeline.  We are still seeing the lack of agents being the major bottleneck here and are looking to add more but we are concerned that going over 1 agent per core will likely make it slower or cause problems with the deployment.  The only documentation I have found that mentions a core to agent count is 24 cores and 4 agents on non hosted devops.  I reached out to MS support and they pointed me here as this is not break fix. 

 

 

0 Replies