Loading
Salesforce now sends email only from verified domains. Read More
Set Up and Maintain Your Salesforce Organization
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Measure Performance for Your Salesforce Org

          Measure Performance for Your Salesforce Org

          Set up your test org and test client, and accurately measure performance.

          A good testing strategy evaluates both performance and scalability. Performance refers to the speed and effectiveness of a system under a given workload within a given time frame. Scalability is the ability of a system to meet its response time or throughput objectives under increasing application and system processing demands. Make your implementation performant and scalable.

          Plan Your Performance Test and Identify Key Personas

          Create an accurate sandbox org and plan your test using key personas.

          We recommend using a sandbox that is a full copy of your production org. Make sure that your sandbox’s data model is similar to production.

          • Draw a system diagram to visualize current and future features, systems, and users that involve Salesforce. For each part of the system, estimate peak load levels, average load levels, and feature use. Consider user arrival rates, login rates, which pages are viewed, and page views per session. If available, any existing site data as a starting point.
          • Calculate the throughput of your system in Requests per Second (RPS). RPS combines inbound XMLHttpRequests (XHRs) and API calls, both of which are supported by Event Monitoring. For help with accessing these metrics, see Using Event Monitoring.
          • Estimate the size and shape of your data, including the number of accounts, users, feeds, groups, and other objects.
          • In your sandbox org, include any complex relationships between your objects, role hierarchies, and sharing rules.
          Note
          Note Sandbox and production orgs exist in different instances, have different hardware, and can differ in performance. These differences can be most noticeable in asynchronous processing and database caching. Don’t use sandbox performance as a benchmark for production performance. Likewise, don’t use production as a benchmark for sandbox performance.

          After your sandbox org is set up, identify the key personas for your org and plan your tests around their page flows. Different personas have different data volumes and data visibility. Performance for a persona with a wide view of your org’s data, like the VP of Sales, can be different from users with more specialized roles. Use your key personas to build a site map and identify likely page flows for each persona.

          Set Up and Run Performance Tests

          Create tests that evaluate your networks, key personas, and data loading.

          Before measuring your org’s performance, measure your browser’s octane score and network latency using the same hardware and network conditions as your users. Resolve any performance issues before testing your org.

          For each test, define the scope of your investigation, what components are involved in the test, and what metrics you want to measure. Run your performance test multiple times to eliminate variance. Run your tests at regular intervals, and take note of any changes in response times and throughput. Performance testing is an iterative process. Finding and solving issues uncovered by your tests can uncover more issues.

          Note
          Note For step-by-step guidance on designing, executing, and analyzing performance tests, use Scale Test. For more information, see Scale Test.

          Salesforce measures performance in Experienced Page Time (EPT). You can measure EPT in four ways.

          Add an EPT counter to the header of your app

          To add an EPT counter to the header of your app, use Lightning Component Debug Mode, or append ?eptVisible=1 to your URL.

          https://MyDomainName.lightning.force.com/one/one.app?eptVisible=1

          Lightning Component Debug Mode slows performance because it doesn’t minify code. Using ?eptVisible=1 has a smaller impact on performance.

          Use the Lightning Usage App to view page and browser performance

          To measure EPT with the Lightning Usage App, select a tab in the Activity or Usage section on the left side of the page. You can view EPT by the browser used, or by page. Because the Lightning Usage App aggregates performance metrics, using the EPT counter can be better for measuring specific pages.

          Build a custom report using Lightning Usage App objects

          To measure EPT with custom reports in the Lightning Usage App, create a report type using a Lightning Usage App object. After you create the report type, build the report using Report Builder. The Lightning Usage App objects aren’t available in your sandbox org and include:

          • LightningUsageByAppTypeMetrics
          • LightningUsageByBrowserMetrics
          • LightningUsageByPageMetrics
          • LightningUsageByFlexiPageMetrics

          Use the Event Monitoring Analytics App to monitor performance with event types

          To measure EPT with the Event Monitoring Analytics App, use the prebuilt Lightning Performance dashboard. You can also use event types to monitor specific aspects of performance. Some useful event types include:

          • Apex REST API
          • Lightning Page View
          • Lightning Error
          • Lightning Interaction
          • Lightning Performance

          In addition to EPT, use browser developer tools to test network throttling, and use automation tools such as Selenium to test page flow performance. Write persona-based load generation scripts using tools such as LoadRunner or JMeter.

          Example
          Example
          • In a single user performance test, you can look at a Lightning page with custom components. For that test, measure EPT, octane score, and network performance.
          • In a large data volume test, you can look at a list view with many records and complex filters. For that test, focus on SOQL performance.
          • When testing API performance, you can look at Account object updates using the SOAP API. For that test, measure request throughput and database time.
           
          Loading
          Salesforce Help | Article