-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
Service Arch 2020-02-10
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Feels like TaskExecutorPool should be looking at getNumAvailableCores, which would be less than getNumCores in a vCPU-restricted container.
size_t TaskExecutorPool::getSuggestedPoolSize() {
auto poolSize = taskExecutorPoolSize.load();
if (poolSize > 0) {
return poolSize;
}
ProcessInfo p;
unsigned numCores = p.getNumCores();
// Never suggest a number outside the range [4, 64].
return std::max(4U, std::min(64U, numCores));
}