AWS Codepipeline is very slow(source to build stage)

Question

Hello, We have an AWS Codepipeline where it has Source stage as Codecommit and build stage as Jenkins(Custom) and then ECS deployment. We observed that moving from Source stage to build stage taking around 40 to 45 min time. The size of our repository is 2.4 GB.  We see that everytime it zip the code and upload the S3 bucket which acts as source repository for Build stage. We are trying to understand why it is taking that much time ? is this behaviour is expected based on repository size ?  
Note: the above mentioned time only to move to build stage( the build time is not counted here)

Answer

Can you explain what actually happens during the source stage? Why does anything need to get copied to or from S3? CodeBuild can read directly from CodeCommit, so if the source is CodeCommit and the build action is CodeBuild, what actually needs to happen during the source stage?

Answer

Hi,  
  
Regretfully, this is likely the expected time for the repository source stage action currently based on the repository. We understand the pain this causes and will take this post as a customer request to improve performance on this aspect of the CodeCommit experience.  
  
The CodeCommit source stages tend to be particularly slow packaging large individual files into the ZIP archives. As a workaround, if you can move some of your largest file assets out into other locations (like S3, for example), then it would very likely have a positive performance impact on the source stage.  
  
Another potential for slowness comes from long delta chains that Git may be creating. If you repack your repository with a smaller delta chain length and re-push to CodeCommit, this may also have some positive performance impact on your Source stage. To do this, run:

```
git repack -adf --depth 15
git push
```

_Note that there must be a new content to push here._  
  
Thanks!

AWS Codepipeline is very slow(source to build stage)

相關內容