TC10 high CPU and slow NuGet indexing

Answered

Hi  - 

Upgraded to TeamCity 10 last week and we are now experiencing problems with our build/deployment pipeline. We are using TeamCity with the internal NuGet Feed and Octopus Deploy. A typical build creates x number of nupkg, publishes to the internal TeamCity feed, creates a new Octopus Deploy release and deploys to a preprod environment. However after upgrading, the nupkg in the TC feed are not indexed at the time of deployment. Viewing the build log, each artifact is indexed at the end of each build step. However it seems that TC10 is a bit slower at this, than TC9.

Anyone experience this? Besides publishing to Octopus Deploy's internal feed, can I tweak this behavior?

Specs: VM, 4 cores, 6GB ram, JVM at 40% Artifact folder: 172GB, 240K files, 90K folders.

Additional information:

CPU load seems to have changes drastically after the upgrade.

3 comments
Official comment

Thanks, will take a look

Unswered on stackoverflow. But we can continue conversation here if it is suitable.

0

Please sign in to leave a comment.