HomeGuidesDeveloper HubRelease Notes
Get supportBook a chat
Guides
These docs are for v2.69. Click to read the latest docs for v2.208.

Promotions

We have done a stress test on programs that include promotions to help you understand the upper limits that you may run into as you grow.

Performance test results for promotions

Based on on our tests, it's possible to assume that an org installed using Fielo with similar configurations and rules complexity will have results consistent with the finding below:

827

The purpose of the online performance test scenario (Virtual users incentivizing members through a web browser) was to understand the limits of promotions under the following configurations:

  • 15k Members: 1 Promotion – 1 Rule – 1 Criteria
  • 40K Members: 3 Promotion – 3 Rules – 3 Criteria
  • 100K Members: 6 Promotion – 6 Rules – 6 Criteria

Salesforce Sandbox configuration:

  • FieloPLT Package Version: Winter 2.63.7
  • Members: 100k registered in a program
  • Levels: 3 levels
  • Segments: 3 segments
  • Promotions: 6 promotions with 6 rules and 6 Criteria’s (2 rules to redeem points)

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 75 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 100 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.


Did this page help you?