Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 for Visual Studio Documentation | 2025.1

# P4 - Data Retrieval

Set the following preferences to determine how P4 for Visual Studio retrieves data from P4 Server.

## Data Retrieval

- Check server for updates every
  Defines how frequently to check P4 Server for file status updates.
  Frequent checks show current status but increase server load.

- Maximum number of files displayed per changelist
  Limits how many files are displayed in a changelist UI.
  Does not limit how many files a changelist can contain.

- Maximum size of files to preview
  Limits the size of image previews in the Preview tab.
  Reduces bandwidth by limiting image data retrieved.

- Number of changelists, jobs, or labels to fetch at time
  Determines how many items are fetched in a batch.
  To fetch all items at once, use 0 as the value.

- Automatically update file status when selection changes
  Updates status badges in Solution Explorer when selecting or hovering over files.
  Disabling this option might improve performance.

## File State Retrieval Optimization

By default, P4 for Visual Studio retrieves metadata for each file individually, which might negatively impact performance in large projects. To improve performance, enable the option that best matches your project size and workflow.

Optimize file state retrieval:

- Optimize Solution Load (Update project glyphs on selection)
  Improves solution loading speed by deferring project glyph updates until files or folders are selected.
  Recommended for large projects such as Unreal Engine.
  To reduce server calls and improves the responsiveness of Visual Studio, this option enables the Automatically update file status when selection changes option and disables the Check server for updates every option.

- Optimize file state retrieval

  - Treat Solution/Projects as directories
    Solutions and projects are handled as directory roots in server commands.
    Avoid using this option if the solution directories contain many other files under P4 Server source control that are not part of the solution.

  - Preload file state
    Preloads metadata for all files under the solution directory.
    Recommended for projects that are entirely under the solution root if the projects are not large.

- Lazy load file state
  Retrieves metadata only when a file is acted upon.
  Best for large solutions where you work on a subset of files such as libraries, assets, or generated content.

  - Full menu
    Enables the full P4 for Visual Studio menu for files before metadata is loaded.
    This allows preemptive operations but might result in errors if the file state is unknown.

- Do not optimize
  For small projects.

Your search for returned results