Budgeting and Rebates

Budgeting allows you to create spending goals and track how your program funds are being spent, all in one convenient place, and rebate is a sales promotion tool that uses payout as an incentive.

The purpose of this performance test scenario was to understand the transactions concurrency limits (transactions being generated at the same time) of these two features.

Salesforce Sandbox configuration

• Members: 1 Million registered in a program
• Team: 50 Thousand teams with approximately 7 team members each
• Levels: 3 levels
• Segments: 3 segment
• 1 challenge per segment and 3 missions per challenge, each mission rewarding payout when completing the mission
• 3 different promotions, one for each segment and each promotion had 3 rules

Performance test strategy

Budgeting

For budgeting scenario, it was created 3 budgets with 10 earmarks and executed the promotion and challenge scenarios with a currency that generates payout called Dollar configured. After delivering the rewards, the budget consumption batch was initiated.

That batch was executed 3 times and the average of batches processed was 59.2 batches per day or 11.8 Million records processed per day. Considering that each batch had 200 records.

Rebate

The rebate scenario, however, was divided in two steps. First, the execution of incentives rewarding payout immediately or periodically, and second executing the Update Payout Status Batch.

In the first step, it was not identified any impact on the performance of the incentives. It was possible to maintain the same performance of approximately 100 transactions per second for promotions and challenges as shown within their respective performance pages.

The second step was performed three times and yielded the following result: 4,000 batches per day, or 817 Thousand records per day. Considering that each batch had 200 records.