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
{{ message }}
Repository navigation
Inconsistency for Num threads calculation if they don't specified #217
in some places it's Math.Max(2, Environment.ProcessorCount - 1)
in others it'sArgs.NumThreads ?? Environment.ProcessorCount;
which is a bit strange. It's either half of cores, all cores, or we left one core to be free.
KMeans, SdcaRegression, LinearClassifier , and BinaryLoader use half of available cores which leads to 50% CPU utilization. @TomFinley, @GalOshri , @glebuk
Activity
shmoradims commentedon Nov 28, 2018
@Ivanidzo4ka i think this issue still needs discussion to define what the fix should be. I added need-info tag for now (feel free to revert)
@eerhardt @TomFinley @Zruty0 could you please discuss a concrete action path for this issue so it can be fixed? Thanks.
Seal API classes (and make EnableCaching internal) (dotnet#217)
code migration from machinelearning-automl to machinelearning repo fe…
Seal API classes (and make EnableCaching internal) (dotnet#217)
Added onnx export functionality for LpNormNormalizingTransformer (#4161)
Added Onnx export functionality to PCATransformer (#4188)
rosebyte commentedon Sep 9, 2026
triage: we will investigate if there is a reason to have the same thread counts everywhere