You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System(s) are you seeing this problem on?
Windows
dlib version
19.24.2
Python version
3.11.7
Compiler
MSVC 19.39.33523
Expected Behavior
Build should set appropriate parallel thread count
Current Behavior
Build only uses 2 threads on 32/64 core machine with 512GB of ram.
Steps to Reproduce
pip install dlib
observe very long build time
Anything else?
A fix for this should be a quick conditional in the num_available_cpu_cores(ram_per_build_process_in_gb) function in setup.py if the os is Windows, something like:
The windows functions should be standard with win python installs but I didn't submit a pull request since I haven't tested this inside that file, I just know the given functions to determine memory work.
The AvailPhys field returned doesn't include pagefile or virtual memory so there shouldn't be any chance of hitting either of those.
Right now it fails and returns 2 because os.sysconf isn't defined on Windows so it throws the exception and uses the default value.
The text was updated successfully, but these errors were encountered:
What Operating System(s) are you seeing this problem on?
Windows
dlib version
19.24.2
Python version
3.11.7
Compiler
MSVC 19.39.33523
Expected Behavior
Build should set appropriate parallel thread count
Current Behavior
Build only uses 2 threads on 32/64 core machine with 512GB of ram.
Steps to Reproduce
pip install dlib
observe very long build time
Anything else?
A fix for this should be a quick conditional in the num_available_cpu_cores(ram_per_build_process_in_gb) function in setup.py if the os is Windows, something like:
The windows functions should be standard with win python installs but I didn't submit a pull request since I haven't tested this inside that file, I just know the given functions to determine memory work.
The AvailPhys field returned doesn't include pagefile or virtual memory so there shouldn't be any chance of hitting either of those.
Right now it fails and returns 2 because os.sysconf isn't defined on Windows so it throws the exception and uses the default value.
The text was updated successfully, but these errors were encountered: