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

Promotions

Concurrency limits

We have done stress tests on programs that include promotions in order 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, was to test different scenarios in order to compare the results and check Fund Allocation Rewarding performance evaluation:

Salesforce Sandbox configuration

  • FieloPLT Version: 2.105
  • Members: 500 thousand registered in a program
  • Accounts enabled as partner: 300
  • Levels: 3 levels
  • Segments: 3 segments
  • Promotion: 3 Promotions (one per each segment) with 3 Rules each
  • Rewarding: 1 currency - Dollar.

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 and rewarding only one currency (Dollar) can safely process 120 transactions per second, as seen in the chart below:

567

In the next chart it is possible to see the number of transactions per second that Fielo can handle when processing Promotions rewarding Fund Allocation:

567

With the following limit and response times:

ScenarioTransactions per SecondAverage response time (sec
Promotion rewarding Dollar120 TPS1,5
Promotion rewarding Funds140 Offline Batch0,65

*TPS = Transactions per second

For the online Promotion scenario, it was possible to notice an improvement on the application performance: in Spring '20, Fielo was able to process 90 transaction per second, while in the current Spring’21 release we are able to process 120 transactions per second. It means 31% of improvement for online scenario.

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.


Did this page help you?