Configuring Uluro to run multiple instances of Breakpack

In its normal configuration, Uluro is capable of processing submissions one at a time in the order they are received. If greater speed is required however, Uluro can be configured to run multiple instances of Breakpack to speed up the processing of new files. This has the benefit of multiplying the number of simultaneous submissions that can be handled at a given time, but it has a cost: For every additional instance of Breakpack that is running, roughly twice the system resources are consumed that a single Breakpack instance uses. As a result, we only recommend running multiple instances of Breakpack if there are sufficient system resources available and even then we suggest starting out with 2 instances at first and adding additional ones after making sure the system can take it. 


Due to the amount of system resources that the BreakPack process takes, it is recommended not to exceed 5 concurrent process per server. If additional concurrent processes are desired or the main system does not have sufficient system resources to run concurrent processes, another system can be setup to be a dedicated processing server. When multiple systems are setup to run the BreakPack processing service, Uluro will automatically distribute the processes across the environments.


Given these resources, there are two parts to enabling the usage of multiple uBrkpackapp.exe instances:

1. In the main Uluro  Applications Database (typically called Uluro) there is a table called ProcessMax.

The table has entries for the handful of programs we have that are capable of running more than one instance, and is set up for optimum performance by default. There is an entry for Breakpack that has its ProcessMax Field set to '1'.

This must be updated to change the number of instances of Breakpack that can run. We strongly recommend starting with setting the field to '2' to start with, then testing for a few days to a week to get an idea how your performance has changed. After setting the ProcessMax field for ProcessName 'Breakpack' to '2' in SQL, you need to make another change.


2. On the Uluro server running the Breakpack service (typically the applications server), you need to edit a registry entry. In the registry, navigate to "HKEY_CURRENT_USER\Software\Transformations\Breakpack" and set the LocalMax key to how many simultaneous programs to run (set to 2).


Once you have done these two steps, restart the Breakpack service. That's it, there's nothing else to do but monitor performance to make sure that your processing times remain optimal.

Disclaimer: Adjusting registry items should only be done by someone who is familiar with editing the Windows Registry. If you are unfamiliar with editing the Windows Registry, please do not attempt this optimization.



Article is closed for comments.
Powered by Zendesk