----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/43144/#review118141 -----------------------------------------------------------
docs/configuration.md (lines 1679 - 1682) <https://reviews.apache.org/r/43144/#comment179392> How about: Libprocess will normally use a thread pool sized according to the number of active CPUs. This can be overridden by setting the LIBPROCESS_MAX_WORKER_THREADS environment variable to the desired thread count. Normally, this will provides an upper bound on the number of worker threads. - Guangya Liu On 二月 5, 2016, 9:46 p.m., Maged Michael wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/43144/ > ----------------------------------------------------------- > > (Updated 二月 5, 2016, 9:46 p.m.) > > > Review request for mesos, Guangya Liu, Klaus Ma, and Qian Zhang. > > > Bugs: MESOS-4353 > https://issues.apache.org/jira/browse/MESOS-4353 > > > Repository: mesos > > > Description > ------- > > Added env var to set upper bound on number of libprocess worker threads. > > > Diffs > ----- > > 3rdparty/libprocess/src/process.cpp d8a74d7 > docs/configuration.md 4b5a394 > > Diff: https://reviews.apache.org/r/43144/diff/ > > > Testing > ------- > > Passed make check on x86_64 Ubuntu 14.04. > > Invocations of mesos-master, mesos-slave, and mesos-tests with the > LIBPROCESS_MAX_WORKER_THREADS set to the values "1", "7", "9", "1000", "0", > "-1", and "abc" on a 4-core x86_64 Ubuntu 14.04 system. The results were as > expected. 1, 7, 8, 8, 8, 8, and 8 worker threads were created, respectively. > The last 3 tests generated warnings. > > > Thanks, > > Maged Michael > >
