Challenges
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 a performance test on Challenges that include Teams using Fielo PLT 2.67.1. The test scenario was to measure the Challenge limits and the response times.
Invoices Limits & Response times
| Scenario | Maximum number of transactions per Second | Create Event Average response time (sec) |
|---|---|---|
| Challenges with teams | 60 TPS / 5.1 Million day | 1.5 Seconds |
*TPS:Transactions per second
Performance Test Results
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 for Challenges with teams.
The data in the graph indicates 60 transactions per second (or 5.1 million per day) can be guaranteed without any issues or errors. Any transactions above 60 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: Summer 2.67.1
- Members: 1 Million registered in a program
- Teams: 164.000
- Challenges: 300
- Missions: 900
- Levels: 3 levels
- Segments: 3 segments
- Storage: 30Gb of usage
Updated about 1 year ago
