Bug #5596
closedWthttpd doesn't take --threads parameter into account.
0%
Description
I have tried both -t and --threads with values below and above 10. Wthttpd always uses the same number of threads regardless of the -t parameter.
By the way, although default thread count is 10 according to the documentation, the process uses 13 or 14 process.
Wt version: 3.3.6 MSVC2013 64bit, prebuilt binaries by Emweb.
Updated by Roel Standaert about 7 years ago
I'm not sure about the 2013 version, but I just checked with the latest master (which should become the Wt 3.3.7 release) and VS 2010 and 2015 and the number of threads used is equal to the threads parameter.
The exact number of threads spawned by the application may differ, though. The threads parameter only controls the amount of threads that service the WServer's underlying WIOService. I've noticed a few extra threads, but those are not directly spawned by Wt.
Regards,
Roel
Updated by Kayra Akman about 7 years ago
The issue is not reproducible with 3.3.7 MSVS2013. Upgrading to 3.3.7 is an acceptable fix.