On Mon, 18 Mar 2002, Alex McLintock wrote: > I've been contacted about a site which is an Apache/mod_perl website. > The problem is that the live production server is Windows 2000 and not > negotiable :-( > > In theory this is ok - Apache and mod_perl should run ok on Windows 2000 > shouldn't it?
For some value of OK. Apache runs as a multi-threaded process under windows, not the *nix multi process model. mod_perl doesn't run multi-threaded. You can only ever run one mod_perl process on windows which means all mod_perl calls have to be serialised. This really kills performance. > Unfortunately when even ultra simple cgi scripts get called the apache > process starts sucking up memory a lot. Apache/mod_perl does use up quite a lot of memeory but there are lot's of techniques for minimising this. The Guide [1] is essential reading. > I'm no expert on Windows boxes - I haven't written a perl cgi script for > one in over a year. Can anyone suggest what I could do to diagnose this > problem? Anyone with experience of Apache and mod_perl on Windows 2000 that > we can email soon with more info? Install linux or use FastCGI. I don't know how the latter behaves under Win2k but if you're not looking to get at the Apache API it might be of help. > I haven't dug my fingers into the problem yet but have read all the > FAQs/Docs I can. Strangely there seems to be no mention of this in the Guide which makes me suspicious that things have change since I last looked at this (approx 12 months ago). Simon. [1] http://perl.apache.org/guide/ -- "So long and thanks for all the fish"
