I don't know if that's intentional or not, but, at least in Wt 3.3.4, the threadpool of the server and session processes are the same; the WIOService's threadPool is set by WServer.C, using the corresponding application option (from wt_config.xml).
If you specifies the num-threads as a command line option or in the wthttpd config file, it overrides the one specified in wt_config.xml. If you don't set the thread-count in the wt_config.xml, it takes 10 by default. In any case, the threadPool is unique, no matter where you specify it. In dedicated process mode, shouldn't be the thread pool different for the main server and for each one of the session processes? Because on the session processes is where user code lives. For example, if I'm afraid about make my app multithreading, I could set the thread-count = 0, but that makes the main server's thread-pool 0 as well, lowering the server responsiveness.
------------------------------------------------------------------------------
_______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
