alien_life_form has asked for the wisdom of the Perl Monks concerning the following question:

Greetings.

I have today come to the realization (at the end of the development cycle: duh!) that - on windows NT - mod_perl serializes all requests (including requests to static pages). Argh.

And the question is:

Is there a solution to this, or am I back to CGI?

I know about perlEx, and I will pursue that avenue if nothing else pops up (porting should be possible, as I am using CGI.pm).

But (as I'd rather avoid IIS, if at all possible) I would like to know if there is a way to salvage the mod_perl solution... perhaps in the apache 2.0 series?

Advanced thanks & cheers

You can't have everything: where would you put it?

Replies are listed 'Best First'.
Re: multithreading mod_perl on Windows NT
by echo (Pilgrim) on Sep 19, 2001 at 00:25 UTC
    With mod_perl 1.x / Apache 1.x the only way is Unix. For Windows NT/2k, mod_perl 2.0 / Apache 2.0 will get rid of this serialization, but they're not beta yet, you might have to wait a while before they reach production quality.
[reply]
      Thank you,
      sort of what I have expected.

      Do you have a link to mod_perl 2?
      Cheers, alf

      You can't have everything: where would you put it?
[reply]
[reply]
Re: multithreading mod_perl on Windows NT
by perrin (Chancellor) on Sep 19, 2001 at 00:56 UTC
    Most people report that serialized mod_perl on NT is still much faster than IIS using Perl as CGI or ASP with PerlScript. If it really won't work for you PerlEx is probably the best option. However, there's also VelociGen which offers a FastCGI-like system that runs on NT with IIS or Netscape servers.
[reply]
      Greetings.

      That may well be, but the problem is that my application runs queries against another application - and these can take a very long time (one of these can last minutes, and here startup/compilation times do not matter much).

      In these cases, mod_perl's serializing behaviour freezes everybody else out,which is wholly unacceptable.

      As a matter of fact, I am somewhat embittered that this fundamental flaw of mod_perl on win32 is not stated more clearly on the module packaging (so to speak).

      Yes, apache.org warns about win32 being not on par with Unix, however this type of shortcoming would appear to warrant a little bit more detail, would'nt it?

      Cheers, alf

[reply]
        Yes, it should probably be pointed out in the mod_perl README. Since Win32 support is relatively new and since none of the documentation maintainers use it, that part of the documentation sometimes suffers. Most of the Win32 support is given on the mailing list, where some people with a lot of knowledge on the subject answer newbie questions.

        The best thing to do would be to send documentation suggestions to Stas Bekman (stas@stason.org) who leads the documentation effort.

[reply]

Back to Seekers of Perl Wisdom