microsoft / microsoft/WSL

Does version 2.6.3 of WSL still not support multiple NUMA nodes?

Open
#14,015 3 comments 0 reactions 0 assignees View on GitHub
feature question
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

### Windows Version

Windows: 10.0.22621.4317

### WSL Version

2.6.3.0

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

6.6.87.2-1

### Distro Version

Ubuntu 24.04.3 LTS

### Other Software

lightgbm 4.6.0

### Repro Steps

When I was training with LightGBM, I noticed that even though I had specified njobs=192, it seems that WSL can still only use one NUMA node and cannot utilize all system resources. Can this be configured?
Do I need to provide other information to identify the problem, or is the current version like this?

Information displayed in lscpu:
Virtualization features:
Virtualization: AMD-V
Hypervisor vendor: Microsoft
Virtualization type: full
Caches (sum of all):
L1d: 3 MiB (96 instances)
L1i: 3 MiB (96 instances)
L2: 48 MiB (96 instances)
L3: 16 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-191

Contributor guide

Open the contributing guide

Research direction

Start with the reported WSL 2.6.3.0 environment and reproduce the LightGBM training case using the supplied lscpu output. Determine whether the single NUMA node is expected or configurable in WSL, and document the result and required configuration or additional diagnostics.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, ubuntu
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.