Fielo Lightning Components
Concurrency limits
Lightning Components are functional units of encapsulated code that empower admins to build Lightning pages visually, without code. They can be used from customizing your Salesforce Org to creating stand-alone apps.
The following list provides the results of the stress test made for the Fielo Lightning Components done with the intention of understanding the concurrency limits (transactions being generated at the same time) that you might run into:
Member Selector and Reward Catalog
Salesforce Sandbox configuration
To understand our testing methods better, we have provided the details of our testing Sandbox configuration:
- Members: 1 Million registered in a program
- Levels: 3 levels
- Segments: 3 segments
- Storage: 20Gb of usage
Member Selector and Reward Catalog
The following graph shows the number of transactions per second for both the Member Selector (blue) and the Reward Catalog (purple) components.
The data in the graph indicates 17 transactions per second (or 1.4 million per day) can be guaranteed without any issues or errors. Any transactions above 17 per second may start to introduce errors and not complete the transaction due to Salesforce limits. The number of rewards available for a member had no impact on the performance.
Profile and My Transactions
The limit of transactions per second of both the Profile and the My Transactions components was the same as the graph above.
Just like the previous graph, the limit of 17 transactions per second (or 1.4 million per day) can be guaranteed without any issues or errors. Any transactions above 17 per second may start to introduce errors and not complete the transaction due to Salesforce limits. The number of transactions and redemptions per member had no impact on the performance.
The following chart shows the response time for all the methods of the Fielo Lightning Components, which was less than a second:
Updated about 1 year ago