all right that 'll save me a lot of hassle...
is mod_perl2 stable enough for production purposes or is it highly not recommended to use it in prod?
apart from that, apache2 gave me impressive results when benchmarking with ab against a single html page. it was able to handle 1400+ hits a sec, whereas apache1 on the same box only handled about 650-700... wow! i've got to figure out if it performs as well in real life though... | [reply] |
It is considered pretty solid in the pre-fork MPM mode (basically the apache 1 model) on popular platforms like Linux. The threaded MPMs are not as safe at this point. For static content, apache 2 is considered stable.
| [reply] |
What's had me up the last day or so is how to deal with the various threading/multiprocessing thingies between ActiveState perl on Win32, mod_perl in Apache 1, Apache 2, plain forking on the various unixalikes. Eventually I'd like to get some XS code running but it's pretty intimidating when that minefield just keeps getting larger and larger...
__SIG__
printf "You are here %08x\n", unpack "L!", unpack "P4", pack "L!", B::svref_2object(sub{})->OUTSIDE
| [reply]
[d/l] |
That is what beta means: not for production. There's also a useful guideline that the first release also isn't for production. Others will jump on it and find some other nasty bugs for you but you only avoid those by letting it sit for a bit until it increments past the x.0 version.
__SIG__
printf "You are here %08x\n", unpack "L!", unpack "P4", pack "L!", B::svref_2object(sub{})->OUTSIDE
| [reply]
[d/l]
[select] |