Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our Perforce server has been operational since July 2, 2013, and the current changelist number is 1524832.
Normally, using changes -m is efficient for both users and build machines due to our optimization settings.
(For more details, see Server performance related to 'p4 changes').
However, retrieving changes for a specific client and revision is significantly slower
(changes -m1 //clientname/...@Rev).
This slowdown affects the plugin's ability to determine the latest changelist number for clients.
I believe that setting a revision range for changes is not essential, and omitting it could enhance performance.
According to the documentation, optimizations are most effective when not restricted by revision specifications.
I have already implemented this change in our Jenkins setup, and it has shown positive results.
Before
After
Testing done
Submitter checklist