Tweak App Action modifies CPU priority for a Windows app or process. It also allows pinning an app to a particular CPU core/thread or multiple virtual CPUs. Overall system performance can be greatly optimized by selecting the correct logical CPUs for an app.
Use the App Monitor or Task Scheduler Triggers to reinforce CPU affinity when the OS scheduler decides to allocate different CPUs to the process.
|Application||Select a process or app to fine-tune:|
|App info||Shows the current status of a process or application, for example:|
The tooltip displays extended process information in real-time.
|Priority||Select one of the standard Windows process priority classes. This will change the CPU priority for all application threads:|
|Priority boost||Enable or disable the ability to temporarily boost performance of the selected app:|
|CPU affinity||Choose a logical CPU or multiple CPUs to allocate for the selected process. Selecting CPUs from multiple NUMA nodes will activate them only from one NUMA node (in most server configurations).|
Depending on your BIOS and Windows configuration a logical CPU is one of the following:
Hover mouse over each CPU to view its properties, such as NUMA node number and which virtual cores are shared with a particular physical core · CPU affinity explained
Use Max / More feature to add additional cores, which are limited by Automation Workshop edition · Compare editions
Adding more cores than your system has will not have any effect when the Task runs, however, it is useful when you are configuring workflows for Remote deployment.
|System configuration||The quick overview shows your current CPU configuration:|
Hover your mouse over the info block to reveal more in-depth CPU information including make and model:
|Start menu||Choose an App using the virtual Windows Start menu. All the necessary app parameters will be prefiled automatically.|
|Browse||Use Browse to select a particular file or folder on local disk, network share on LAN (local area network), etc.|
|Variable Wizard||Use dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc.|
In Windows, an app or background process can have multiple instances of the same executable running concurrently. You have three options to choose from:
- Selecting an app from the provided list by its name will modify all instances of the app.
- Typing a name of the app manually will also tweak all instances of the app.
- Providing a specific Process identifier (PID) of the app or process will only tweak the specified instance. The PID can be obtained using Variable Wizard from other Actions.
It's important to note that the first two options are used to tweak all the instances of the running app, whereas the last option is for modifying only the specific instance of the app.
While Automation Workshop doesn't have hardcoded limits, your system configuration and Windows edition can limit the available number of CPUs, cores, threads, and NUMA nodes.
- It is recommended to execute the Task using the SYSTEM user account or, at least—with a user account that has administrative privileges.
- The 32-bit version of Automation Workshop is limited to the first 32 cores (0–31 vCPU) in the 1st NUMA node. However, if your workflow is designed to be run on a remote machine, the Max / More feature can be used to add more CPUs.
Ask for more…
If you have any questions, please do not hesitate to contact our support team.