Hi Stefan, I quite agree with you that a table will be a good idea. Maybe the best way for some settings will be to create a formula.
Something that depends on system environment and user/vhost requirements. # here are some of my settings for my small devel server with peruser 0.3 # ServerLimit ?= MaxClients = (RAM - size_all_other_processes)/(avg_size_apache_process) ServerLimit 250 MaxClients 250 MinSpareProcessors 1 MaxSpareProcessors 0 MinProcessors 1 MaxProcessors 15 MaxRequestsPerChild 1000 ExpireTimeout 7200 IdleTimeout 300 MinMultiplexers 1 MaxMultiplexers 5 MultiplexerIdleTimeout 120 Multiplexer apache apache ProcessorWaitTimeout 10 KeepAlive On MaxKeepAliveRequests 100 KeepAliveTimeout 1 I would consent to create a JS app for you. - Stefan --- Original Nachricht --- Absender: Stefan Klingner Datum: 03.12.2009 22:19 Uhr > i think writing a table with test results for different configurations > would be usefull to find optimal way for configuration. what do you > think should this table contain to be usefull? > > Stefan Rieger schrieb: >> Hi >> >> I've tried some weeks ago the 0.4 Patch (not rc1) on an productiv system >> with 972 vHosts and 440 users with the same problems. After a view Minutes >> we got no Response from the Server. >> >> System MemTotal: 8,313,596 kB on AMD Opterons >> >> Which config settings are recommendable? >> >> Maybe i can test it again ... late at night ;) _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
