Challenge and Promotions
Concurrency limits
We have done stress tests on programs that include promotions and challenges running in parallel that have or don’t have capping applied to help you understand the upper concurrency limits (transactions being generated at the same time) that you may run into as you grow.
The purpose of the online performance test scenario (Virtual users incentivizing members through a web browser) was to understand the limits of promotions and challenges in parallel where there were 3 different promotions and challenges, one for each segment and each promotion had 3 rules and challenges had 3 missions.
Performance Test Results for Challenges and Promotions running in parallel
In this scenario we could reach the maximum number of 50 transactions per second and the response time was 3 seconds for each request.
| Scenario | Transactions per second | Average response time (sec) |
|---|---|---|
| Challenge & Promotion | 50 TPS | 3 Seconds |
*TPS = Transactions per second
The following graphic shows the number of transactions (a transaction would be any the program needs to process something related to the promotion and challenge) per second that Fielo can handle when we have promotions and challenges running in parallel.
The data in the graph indicates 50 transactions per second (or 4.3 million per day) can be guaranteed without any issues or errors. Any transactions above 50 per second may start to introduce errors and not complete the transaction.
Salesforce Sandbox configuration
- Members: 1 Million registered in a program
- Levels: 3 levels
- Segments: 3 segment
- 1 challenge per segment and 3 missions per challenge, each mission rewarding payout when completing the mission
- 3 different promotions, one for each segment and each promotion had 3 rules
Updated about 1 year ago