I was just expressing my opinion, in the end, you decide, you're the developer. Though it might be worth noting that CPUs and memory on modern VMs can be hot-plugged, so be careful. Would also be cool if the server could log at startup the auto-determined amount of maximum possible connections / clients it can handle.
Thanks. On Friday 02 December 2011, Igor Galić wrote: > ----- Original Message ----- > > > > > If you count all those chars, you'll get 1920. Anybody knows > > > > what's going > > > > on? > > > > > > yep. ServerLimit * ThreadLimit (defaulted) = 30 * 64 = 1920 > > > > Hmm, that's indeed the case. I was perplexed by wording there. > > Those ServerLimits and ThreadLimits could be set automatically, based > > on > > user's impression of maximum amount of connections he wants the > > server to > > handle. > > That's sort of what MaxRequestWorkers (the artist formerly know as > MaxClients) is for: > > http://httpd.apache.org/docs/trunk/mod/mpm_common.html#maxrequestworkers > > The only problem is that you still have to scale those other two > to get there. I am still of the opinion it would make sense to > scale those automagickally: We define (an arbitrary, perhaps sane) > default for MaxRequestWorkers. Using a library such as hwloc to > determine the CPU topology (and the amount of available memory) we > then auto-scale ServerLimit and ThreadLimit and ThreadsPerChild. > > > Thanks for help. > > > > -- -- Best regards, Yuri Arabadji -- Systems Engineer
