Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What causes high CPU load on agents when cloning repositories?



if I use the Source Code Checkout task cloning the repository takes up to 9 minutes. Most of the time is spent in these steps

01:43:17 Fetching 'refs/heads/*' from 'ssh://'.
01:43:17 Warning: Permanently added '[]:36431' (RSA) to the list of known hosts.
01:51:55 From ssh://
01:51:55 * [new branch] mybranch

During this time the CPU load of the agent running on an AWS EC2 machine (c4.4xlarge) goes up to 100% using only one of the available 8 cores.

If I use a Script task to execute

git init myproject
cd myproject
git remote add origin ssh://
git fetch

cloning is much faster

14:48:59 Initialized empty Git repository in /root/bamboo-agent-home/xml-data/build-dir/MY-PROJ-JOB1/myproject/.git/
14:48:59 Warning: Permanently added '[]:7999,[]:7999' (RSA) to the list of known hosts.
14:49:47 From ssh://
14:49:47 * [new branch] mybranch

What is causing this high load and how can I make cloning repositories faster?

1 answer

0 votes
Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 08, 2022

Hi @Clifford Sanders

this could be hard to pinpoint from the outside/from Community so I am only able to share some more generic information - the first attempt for diagnosing performance issues could be to follow the troubleshooting guideline.

In case the issue is still current and you have not reviewed the information recorded here, it could give a first clue:


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events