Can we specify which NUMA WSL will run on?

[muratyurdakul75]

There are 2 NUMAs in my system. Numa 0 and 1. WSL always uses numa 1. Is there any way to make it use numa 0?
When the computer starts, wsl starts automatically and I want it to work on NUMA 0. Is there a solution for this?

I don't want to use external applications. Can we do this feature directly with Windows or WSL settings?

Thanks

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• Multiple NUMA support (#11301), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• Multiple NUMA support (#11301), similarity score: 0.72

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[muratyurdakul75]

/question

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[muratyurdakul75]

WslLogs-2024-11-26_20-14-12.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.3.26.0

[zcobol]

@muratyurdakul75 in Task Manager try seting process affinity for wslservice.exe to use the CPU associated with NUMA 0 only.

[muratyurdakul75]

@muratyurdakul75 in Task Manager try seting process affinity for wslservice.exe to use the CPU associated with NUMA 0 only.

Thanks for your answer. But setting it from task manager is not a solution. There is a situation like this; I have 2x40 processors. I want WSL to use more processors. With the "node interleaving" setting I made from BIOS, I was able to arrange the numbers as 64+16. Numa:0 has 64 processors, Numa:1 has 16 processors. When wsl first runs, it uses Numa:1. That is, 16 processors. Even if I set it as numa:0 from Task Manager, when I look with the "Docker info" command, I see that it uses 16 processors. Therefore, when wsl first runs, it needs to run directly with numa:0.

[muratyurdakul75]

It would be great if we could adjust this with a setting in the .wslconfig file.

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'