¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. DXLab
  2. Topics

Graphics cards and Monitors for the shack/ DXLab (about setting affinity)

 

About the application's affinity being transient. There is at least one way to set the affinity with DXLab Launcher. Here is the command line that I use to start WSJT-X in the Apps Started Before DXLab Apps tab:
?
C:\WINDOWS\system32\cmd.exe /C start /affinity 0x7 C:\Users\Public\wsjtx_2_7_0\bin\wsjtx.exe
?
This sets the affinity to processors 0, 1 and 2. The hex code 0x7 is a bit mask where LSB represents CPU0, the next bit CPU1 and so on. So for example for CPUs 2 and 3 you would use hex code 0x0C.
?
Here is how I start SpotCollector from the Apps Started After DXLab Apps tab:
?
C:\WINDOWS\system32\cmd.exe /K start /affinity 0x8 c:\Users\Public\DXLab\SpotCollector\SpotCollector.exe
?
I use the option /K, which leaves the window for cmd.exe running, beacuse otherwise I couldn't terminate SpotCollector with the Launcher. Termination method Close would need a static main window caption, which SpotCollector doesn't have and the kill method needs a running parent process (cmd.exe) for the Termination to work. So I choose the kill method in the Launchers Termination box.
?
I have of course disabled SpotCollector in the Launcher's DXLab Apps tab.
?
If I need to start SpotCollector manually I have to start it from the Apps Started After DXLab Apps tab's Start button, if I want to have the affinity set.
?
--
73 de Tapio at station OH3HN
?
?
On Sat, Apr 12, 2025 at 09:20 PM, Dave AA6YQ wrote:

+ AA6YQ comments below
I understand to go into Windows Task Manager, Details tab, and Set Affinity to accomplish this.? I am finding, that when Spot Collector is terminated and restarted, I have to do it all over again.? I don't see a method to "Save" the affinity that I have set.
+ Setting an application's affinity is indeed transient; it is reset when the application is restarted, and when Windows is rebooted. There are several Windows automation tools that can be used make this automatic: Automation Workshop, Process Hacker, and Anvir Task Manager. I have no experience with any of them. My advice is to first determine whether assigning DXLab applications to cores yields a significant performance improvement in your usage scenario before taking this step
?
?
?
 

+ AA6YQ comments below
About the application's affinity being transient. There is at least one way to set the affinity with DXLab Launcher. Here is the command line that I use to start WSJT-X in the Apps Started Before DXLab Apps tab:
?
C:\WINDOWS\system32\cmd.exe /C start /affinity 0x7 C:\Users\Public\wsjtx_2_7_0\bin\wsjtx.exe
?
+ The free Process Lasso tool enables your to specify persistent core affinities:



? ? ? ?73,
?
? ? ? ? ? ? ? ?Dave, AA6YQ
 

Do you need to keep Process Lasso running all the time, or can you run it once, set your parameters, and then exit?

Thanks,
Earl / KD5XB



Sent with secure email.

On Monday, April 21st, 2025 at 1:48 AM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below
About the application's affinity being transient. There is at least one way to set the affinity with DXLab Launcher. Here is the command line that I use to start WSJT-X in the Apps Started Before DXLab Apps tab:
?
C:\WINDOWS\system32\cmd.exe /C start /affinity 0x7 C:\Users\Public\wsjtx_2_7_0\bin\wsjtx.exe
?
+ The free Process Lasso tool enables your to specify persistent core affinities:



? ? ? ?73,
?
? ? ? ? ? ? ? ?Dave, AA6YQ
 

+ AA6YQ comments below
Do you need to keep Process Lasso running all the time, or can you run it once, set your parameters, and then exit?

You do not need to keep the Process Lasso user interface (GUI) running at all times for your rules and optimizations to remain active. Process Lasso is designed with a separation between its GUI (ProcessLasso.exe) and its core engine, called the Governor (ProcessGovernor.exe):

  • The GUI is used for configuration, monitoring, and displaying the system tray icon, but it does not enforce any rules itself.

  • The Governor is a background process or service that actually applies and enforces all your rules and optimizations.

Once you have set your desired parameters and rules using the GUI, you can close the GUI application. The Governor will continue to run in the background, using minimal system resources (typically 1¨C3 MB of RAM and almost no CPU), and will keep enforcing your settings.

If you want the absolute minimum resource usage, you can configure Process Lasso so that only the Governor runs, without the GUI or system tray icon.

Summary Table

Component Process Name Needs to Stay Running? Role
GUI ProcessLasso.exe No Configuration, monitoring, tray icon
Governor (Core) ProcessGovernor.exe Yes Enforces rules in the background
?

In short:
You only need to keep the Process Lasso Governor running for your rules to be enforced. The GUI can be closed after configuration.

Citations:

Answer from Perplexity:


? ? ?73,

? ? ? ? ? ?Dave, AA6YQ

1 - 4 of 4