Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
See Changes Identified by Source Tracking
Pulling and Pushing Changes Identified by Source Tracking
Resolve Conflicts Between Your Local Project and Org
Get Change Information by Querying the SourceMember Object
Best Practices
Differences and Considerations
Performance Considerations of Source Tracking
Retrieve and Pull Changes to Profiles with Source Tracking
Run force:mdapi:deploy Instead of force:source:deploy with Source Tracking
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Performance Considerations of Source Tracking

Source tracking performs extra functions to determine changes to source tracked components, such as running more queries. So, some commands can take a little longer to run when working with medium-to-large sized projects. If you’re working with small projects, you don’t notice any slowdown.

A medium-sized project has 30 or more components or 50 or more tests. A project with 25 components and 51 tests is considered medium.

A large-sized project is 600 or more components or 150 or more tests. A project with 610 components and 140 tests is considered large.

  • sfdx force:mdapi:deploy
  • sfdx force:source:deploy
  • sfdx force:source:pull
  • sfdx force:source:push
  • sfdx force:source:status

If you experience long-running commands, break up your projects into smaller sets of components, and deploy the smaller sets.