Recommended number of threads per node for PaidMediaSync

Updated on August 3, 2022

By default, the queue processor has two threads per node. You can modify the number of threads based on the specifications of your environment.

Pega Customer Decision Hub Paid Media Manager User Guide

Environment description	Recommended number of threads
Production environment Large customer segments Real-time containers with millions of requests Multiple paid destinations	5 Note: For best performance results, most production environments should use this option.
Production environment Small customer segments Real-time containers with thousands of requests Few paid destinations	2
Testing environment	Any number between 1 and 5, depending on testing loads and observed performance

For general information about increasing the performance of queue processors, see How do I increase the performance of my queue processors?

Changing the number of threads per node for PaidMediaSync
Enabling background processing
Include your application in background processing to enable several functionalities of Pega Customer Decision Hub, such as file and database templates, the processing of event-triggered actions, resilience checks for customer segments, and others.

Previous topic Configuring the PaidMediaSync queue processor to optimize performance
Next topic Changing the number of threads per node for PaidMediaSync

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center