Promotions

We have done stress tests on programs that include promotions that have or don’t have capping applied to its rewards in order to help you understand the upper limits 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 in scenarios where there were 3 different promotions, one for each segment and each promotion had 3 rules.

Salesforce Sandbox configuration

• FieloPLT Package Version: Spring 2.92.3
• Members: 1 Million registered in a program
• Team: 50 Thousand teams with approximately 7 team members each
• Levels: 3 levels
• Segments: 3 segment

Performance test results for promotions

Based on on our tests, it's possible to assume that an org installed using Fielo with similar promotion configurations and rules complexity can safely process 100 transactions per second, as seen in the chart below:

With the following limit and response times:

*TPS = Transactions per second

Based on these results, it is possible to ensure that capping did not have any impact on program performance.

Performance test strategy

The test was performed using the Jmeter load generator tool and installed on AWS instances spread across the globe. The test started with 350 concurrent virtual users creating events that match the promotion rules every 3 seconds.

This number of virtual users and the frequency of creating an event was possible to achieve 110 transactions per second. Every 10 minutes, we kept adding another 50 virtual users until we found the breaking point. As you can see in the graphic above, the responses from Salesforce started to fail when we tried to cross the line of 125 transactions per second done by the 450 virtual users.

This means the Fielo platform can handle 8.6 million transaction per day, independent of how many members are subscribed, or the number of promotions in your program.

📘

The performance of the bulk operation can be impacted by having Related Data Condition configured in the Promotion. In our tests, we managed to reach 580 transactions per second without the Related Data Condition set up and, with it configured, it reached 294 transactions per second.