Code deployment is slow when code repositories include binary files in Puppet Enterprise

After you add some custom code modules, code deployment takes a long time and might time out. The modules that you use from the Puppet Forge aren’t causing any code deployment performance issues.

Version and installation information

PE version: All supported

Solution

When you deploy code that has large files in it, such as binary files, code deployment might be very slow, or might fail.

Depending on how .gitattributes is configured, Git might interpret characters in raw binary files as carriage returns, causing code to be truncated, ignored, or misinterpreted. This causes deployment to take a long time or time out.

You can check if you have an issue with slow code deployment by installing and using the puppetlabs-puppet_operational_dashboards module and checking the File Sync Metrics dashboard.

To avoid this issue, do one of the following:

• Don’t store binary files in your module repository.

• Configure .gitignore to prevent binary files from being committed to your module repository.

• Make sure that binary files in your module code repos are compressed (tarred or zipped) so that your version control doesn’t misinterpret carriage returns and cause code deployment performance issues.

Then, re-deploy the code.