If one build is to @CHANGE and the next run is to @STATIC_LABEL, the p4 plugin calculates the changes by running:

p4 changes -m20 <path>@CHANGES,@STATIC_LABEL

This can be a performance hog especially when the number of tagged files in the label is large.  This affects other uses as it takes massive read locks on db.rev.

Request a way to avoid the p4 changes or fix the performance on the p4d server.