Scale Test’s Limits and Suggested Usage

• The Scale Test environment isn’t an exact replica of your production but rather a production-like configuration to the best of Salesforce’s capabilities.
• Features are active only after the purchase of a Scale Test license. The Restricted Product Approver (RPA) process includes a certain number of days for lead time.
• After you visit Scale Test for the first time, you’re automatically opted into the collection of telemetry data. We use this data to provide scale test and execution insights. It takes 2 or 3 days after your first visit to populate.
• If it's your first time using the Load Generation feature, setup can take more than two weeks.
• All communications about Scale Test booking are in the app or from the account team.
• The instance isn’t an isolated setting. Other customers in the instance perform low or medium-scale activities.
• You can only book scale test days in the same sandbox where you intend to test.
• The information that you request when booking a test slot is final and must coincide with the actual test stats, including:
  • Requests per Second (RPS)
  • Max user logins per minute, as inputs beyond the maximum number of 60 are rejected

Capacity Evaluations

• You have the option of requesting a Capacity Evaluation from your account team to make sure that you have the right environment for your updates.
• If you've run a scale test, including those results in your request is especially useful.

Key Event Management for Signature Support Customers

• While not required, we recommend that our Signature support customers request a Customer Peak Readiness (CPR) review at least 3 months before their peak date.
• A CPR review triggers the Key Event Management (KEM) engagement. This response prepares customers in need of more support during their single most important event of the year.
• Conduct your scale test and share the results with KEM at least 2 weeks before your peak date.