Server Data

You can configure how much data P4V processes during a session to minimize server load for frequently-run commands and large data transfers. The following settings are available:

Check server for updates every n minutes: Specifies how often P4V checks the Perforce service for updated file information. Frequent checks enable P4V to display current file status but increase the workload on the Perforce service.
Maximum number of files displayed per changelist: Specifies the maximum number of files displayed in a changelist, to help minimize the time required to handle and submit very large changelists. This setting affects only the display of changelists and does not limit the number of files that a changelist can contain. Any files beyond the maximum number are displayed as a plain text list.
Maximum size of file to preview (excludes audio and video files): Limits the size of image files displayed in the Preview tab on the Files pane, to limit the amount of image data sent from the Perforce service to P4V.
Number of changelists, jobs, branch mappings or labels to fetch at a time: Specifies the number of specifications read in each batch fetched, to minimize server load and maximize P4V performance. To retrieve all entries, specify 0.
Maximum number of files to display in Dashboard Workspace Folder View: Limits the number of files displayed in the Dashboard view.
Disable parallel sync: Disables concurrent transfer of files for all P4V connections. There is no configuration in P4V to turn on parallel sync; instead, parallel sync is enabled automatically when the net.parallel.threads config parameter is set in a server (2014.1 or later). Parallel sync can greatly reduce the amount of time it takes to update a workspace, especially when connecting across a high latency network. For more information on parallel processing, see Using parallel processing for submits and syncs in Helix Core Server Administrator Guide: Fundamentals.
Disable parallel submit: Disables concurrent transfer of files when submitting to a 2015.1 or later server. Similar to parallel sync, parallel submit can greatly reduce the amount of time required to submit by transferring multiple files across the network at the same time. For information on the server configurables pertaining to parallel submit, see net.parallel.submit.threads and net.parallel.max in the P4 Command Reference. Parallel transfer mode only kicks in if you set net.parallel.max to a value larger than 0.
Disable parallel shelve: Disables file transfer in parallel mode. Parallel shelving is enabled when the net.parallel.shelve.threads config parameter is set in a server (2017.2 or later). By default, this setting is turned on. For more information on the server configurable, see net.parallel.shelve.threads in the P4 Command Reference.
Automatic Safe Resolve (no merging) when syncing files: Automatically resolves differences when getting a file revision by either accepting the target file or the source file, depending on which file has changes. By default, this setting is turned on. When turned off, P4V opens the Resolve dialog instead to let you decide how to resolve differences.