Udostępnij za pośrednictwem

AT degradation when multiple instances of GenCheckinNotesUpdateWortItem task are happening concurrently ...

  • Artykuł

Investigation for the observation made in post.

"CPU consumption on AT went up to the maximum of 38% (w3wp.exe) while the GenCheckinNotesUpdateWorkitem task was executing on the build machine."

Case 1 - 3 msbuild processes in separate window - running GenCheckinNotesUpdateWorkitem on same team project for the first time

  • 5000 changesets distributed over 5000 files
  • Results
    • Max CPU spike – 29% (on AT)
    • Avg CPU ~ 7% to 14%
    • Total time taken - ~ 17 mins

Case 2 - 3 msbuild processes in separate window – running GenCheckinNotesUpdateWorkitem on same different project for the first time

  • 5000 changesets distributed over 5000/400/4 files
  • Results
    • Max CPU spike – 34% (on AT)
    • Avg CPU ~ 7% to 14%
    • Total time taken - ~ 15 mins

Conclusion -

 

There are no issues in running multiple instances of builds concurrently for the same AT.