Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Apache 2.0 Thick/Thin 5 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • How did your think/thin Apache2 experiment go? Google only found this journal entry, where have you seen this technique used before?

    --
    -- "It's not magic, it's work..."
    • I can't remember getting too far futher with it to be honest. I've configered Apache 1.3 with the thick/thin setup a couple of times, using either seperate binaries, or two different shell scripts to run two apaches from the same binary ( using DSO's for the relevant modules ) - This is quite heavily documented, but may not be what you are looking for ( perl.apache.org [apache.org] ), along with using squid for the same purpose, although I have an irrational fear of squid, so have never used that configeration.

      I seem

      • I've seen the technique advocated a number of times, either a simple Apache front end or with a dedicated Squid proxy, and the a complex heavy Apache/mod_perl backend. I've never actually tried it myself, hence my interest in your experience.

        My feeling was that as Apache shares mod_perl memory so to run Apache/mod_Perl in think/thin you'd need to run two instances rather than two virtual servers in the same instance, though I'd like to be proved wrong.

        The kernel server you are think of is called TUX [redhat.com], an

        --
        -- "It's not magic, it's work..."
        • I may be revisiting this area soon, so I'll let you know how I get on. I'm not ready to throw mod_perl 1.9x/2.0RC into production yet, but I'm yet to decide between a fat apache 1.3 and apache 2, or a dual apache 1.3 config.

          My gut feel was that I wouldn't save any memory by using the thick thin virtual server config ( though I probably ought to check ), but I'm a bit cautious when it comes to testing, and often have multiple versions of the same mod_perl app running on different apaches on the same physical server - it lets me test upgrades and dependencies, and is very good for team working. By replicating the "feel" of a thick thin environment, my objective was to simulate the app without the hassle of starting and stopping different apaches in x different instances.

          Thanks for the link to TUX, although I'll probably heed your advice and leave kernel to do kernel things, and let http take care of its self in application space.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.