[JIRA] (JENKINS-62158) Bad performance on EC2 instance for first build

6 views
Skip to first unread message

daniel.hoerner@vyaire.com (JIRA)

unread,
May 4, 2020, 10:37:03 AM5/4/20
to jenkinsc...@googlegroups.com
Daniel Hoerner created an issue
 
Jenkins / Bug JENKINS-62158
Bad performance on EC2 instance for first build
Issue Type: Bug Bug
Assignee: FABRIZIO MANFREDI
Attachments: 2020-05-04 16_31_11-Window.jpg
Components: ec2-plugin, pipeline
Created: 2020-05-04 14:36
Environment: Jenkins ver. 2.220
Labels: ec2-plugin pipeline jenkins
Priority: Major Major
Reporter: Daniel Hoerner

I have a pipeline project which should run at a EC2 instance node.

I have configured an EC2 connection and starting EC2 t3.medium Windows 10 instances automatically. This all works fine.

But, the first build at an EC2 instance always performs very bad (slow!!). The next build at the same instance (without rebott etc) is much more faster.

 

@Library('BMS-Libraries')
import static bms.mail.Email.*
import static bms.nexus.Nexus.*
import static bms.utils.Utils.*node('AWS_VS2017') {
		stage('Cleanup Build Machine'){
			//deleting current workspace directory
			deleteDir()
		}
		
		stage('Preparing Build machine...'){			retrieveAndExtractBuildTools(this)
		}

//Do some more .......
}

I attached a screenshot of the runtime of the different pipeline steps.

 

I connected via RDP to the instance during first build nad task-manager didn't display a high CPU or Memory consumption

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

daniel.hoerner@vyaire.com (JIRA)

unread,
May 4, 2020, 11:29:02 AM5/4/20
to jenkinsc...@googlegroups.com
Daniel Hoerner updated an issue
Change By: Daniel Hoerner
I have a pipeline project which should run at a EC2 instance node.

I have configured an EC2 connection and starting EC2 t3.medium Windows 10 instances automatically. This all works fine.

But, the first build at an EC2 instance always performs very bad (slow!!). The next build at the same instance (without rebott etc) is much more faster.

 
{code:java}

@Library('BMS-Libraries')
import static bms.mail.Email.*
import static bms.nexus.Nexus.*
import static bms.utils.Utils.*
node('AWS_VS2017') {
  stage('Cleanup Build Machine'){
   //deleting current workspace directory
   deleteDir()
  }
  
  stage('Preparing Build machine...'){

   retrieveAndExtractBuildTools(this)
  }

//Do some more .......
}
{code}

I attached a screenshot of the runtime of the different pipeline steps.

 

I connected via RDP to the instance during first build nad task-manager didn't display a high CPU or Memory consumption
Reply all
Reply to author
Forward
0 new messages