No ratings

Package and Deployment CPU Utilization goes to 100%


Package and Deployment CPU Utilization goes to 100%

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


During the creation of packages on Package and Deployment while adding items to your package, the CPU utilizations goes to 100% and takes a long time to complete.




The issue could be caused by system resources, the number of artifacts being added to the package, or the number of dependencies of the artifacts being added.

Troubleshooting Steps

Make sure that your deploying server is configured to run with more than 1 Virtual Processor. If it can't run more than 1 thread at a time, it will comsume 100% CPU and can take a long time to complete.

You can also try and lower the thread priority of the Package and Deployment client in Task Manager.


Alternatively, you can deploy from a different client that has multiple processors.


Please note: Performance is an ongoing feature in K2 that is being optimized. To work with the best performance we recommend you upgrade to the latest version of K2, and install the latest updates and fix packs.


Use the following link for the recommended Server Specifications:


Labels: (2)
Version history
Last update:
‎05-19-2021 11:20 AM
Updated by: