Open topic with navigation
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.
- 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 Versioning Engine Administrator Guide: Fundamentals.
- Enable parallel submit: Enables concurrent transfer of files
when submitting to a 2015.1 or higher 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.