This article explains how to request and run performance and scale tests in Salesforce, including the difference between performance tests (at or below 120 RPS) and Scale Tests (above 120 RPS).
Important: Salesforce Support cannot design or interpret customer scale test results. Support's role is to monitor test activity and confirm that there are no issues with Salesforce services during testing.
RPS (Requests Per Second) is the metric used to measure the volume of inbound traffic during a performance or scale test.
If you have questions about Scale Testing — including test design, execution, best practices, or result interpretation — work with your AE to engage the Salesforce Success teams.
To request a performance test at 120 RPS or below, contact Support via the Salesforce Help site. Submit an LAP request for approval at least one week before the testing date. Requests without advance notice are denied unless categorized as urgent.
Your test plan must include:
A copy of the test plan that you created in Scale Test (image shown for example only).
Changes and customizations to your Salesforce implementation can impact performance. For testing above 120 RPS, use the Salesforce Scale Test product.
To get started:
Contact your customer success representative or account executive for access. In Setup, search for Scale Test in the Quick Find box.
Scale Test is a paid add-on for full sandbox users. It validates a Salesforce implementation's ability to handle production-level traffic using metrics such as RPS, Experienced Page Time (EPT), and server-side traffic.
Before testing, review Salesforce Developer Limits. Exceeding these limits can result in throttling.
Steps to create your test plan:
A Performance Test is for testing at 120 RPS or below and is requested via the LAP process through Salesforce Support. Scale Test is for testing above 120 RPS and requires a paid add-on and coordination through your Account Executive.
Not necessarily. Salesforce Support does not validate testing methodology, debug testing scripts for errors, or confirm that scripts accurately reflect real-world production scenarios.
Support recommends for all test execution frameworks:
No. All tests must be pre-approved. Unapproved testing is subject to throttling or blocking. Pre-approval allows Salesforce Support to schedule Site Reliability (SR) and Customer Centric Engineering (CCE) resources and to monitor the test. Even approved testing can be throttled if it degrades performance on the instance.
Salesforce does not provide overall metrics or server logs for the testing period. For specific requests — such as CPU time for a particular process or details to troubleshoot an error — Support can sometimes extract a limited set of server log data. Work with your support agent.
Proactive Monitoring (PRoM) works alongside Scale Center as part of Salesforce's scalability suite. Use Scale Center for performance monitoring, analysis, and on-demand Lightning Experience Insights.
Salesforce Help: Scale Test Overview
Trailhead: Scale Test Quick Look
Trailhead: Peak Load Tests with Scale Test
000387059

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.