Challenges
Concurrency limits
Challenges are a way of encouraging members to perform particular behaviors and drive engagement. Challenges can be addressed to different audiences (depending on Segmentation) within a specific time period and may go through a range of statuses along the way.
Challenges include one or more Missions, which may include Objectives.
We did performance tests on Challenges and Challenges that include Teams using Fielo PLT v2.105 and v2.92.3. The test scenario was to measure the Challenge concurrency limits (transactions being generated at the same time) and the response times.
Performance Test Results for Challenges
The purpose of the online performance test scenario (Virtual users incentivizing members through a web browser) was to understand the limits of transactions related to challenges in a scenario where there were 1 challenge per segment, and 3 missions per challenge, each mission rewarding payout when completing the mission.
The limits and response time can be found below. Based on these results, it is possible to ensure that capping did not have any impact on program performance.
| Scenario | Transactions per Second | Average response time (sec) |
|---|---|---|
| Challenge Rewarding Dollar | 90 TPS | 1,5 |
| Challenge Rewarding Funds | 65 TPS | 1,3 |
*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 challenge) per second that Challenges can handle.
The data in the graph indicates 90 transactions per second (or 7.7 million per day) can be guaranteed without any issues or errors. Any transactions above 90 per second may start to introduce errors and not complete the transaction.
Salesforce Sandbox configuration
To understand our testing methods better, we have provided the details of our testing Sandbox configuration:
- FieloPLT Version: 2.105
- Members: 500 Thousand registered in a program
- Accounts enabled as partner: 300
- Levels: 3 levels
- Segments: 3 segments
- Challenge: 3 global challenges with 3 mission based on a fixed metric each
Performance Test Results for Challenges that include Teams
The limit and response time for challenges that include teams can be seen below:
| Scenario | Maximum number of transactions per Second | Create Event Average response time (sec) |
|---|---|---|
| Challenges with teams | 100 TPS / 8.6 Million day | 1.8 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 challenge) per second that Challenges with teams can handle.
The data in the graph indicates 120 transactions per second (or 10.2 million per day) can be guaranteed without any issues or errors. Any transactions above 120 per second may start to introduce errors and not complete the transaction.
Salesforce Sandbox configuration:
To understand our testing methods better, we have provided the details of our testing Sandbox configuration:
- FieloPLT Package Version: Winter 2.92.6
- Members: 100k registered in a program
- Levels: 3 levels
- Segments: 3 segments
- Storage: 30Gb of usage
- Teams: 50 Thousand teams
- Team Member: 300 Thousand team members
- Challenges: 163 Challenges
- Missions: 489 Missions
- Rewards: Dollar and Instant rewards
Updated about 1 year ago