Hello,
Apache is my weak hand so hope to clear some fog with your help.
we're looking for a way to offer version handling to our serverside
perl app.
Each database is tagged to a certain version of the application and
they should be upgraded individually to interfere as little as
possible w
On Dec 7, 2005, at 2:03 PM, Frank Wiles wrote:
memcache and other daemons could help out here but they take too much
time compared to perls internal data memory to access and write.
Since they are not really fit for complex hash trees without doing a
heck of data coping forward and back.. i woul
On Dec 7, 2005, at 10:09 AM, Tom Schindl wrote:
Was running prefork apache 2.0.52 earlier. without any of these
symptoms..
Im switching to the worker in an attempt to improve the performance,
I don't think that you gain much performance at least on the mod-perl
side of the story because a you
On Dec 6, 2005, at 7:00 PM, Frank Wiles wrote:
And im not starting up new threads myself.. i rely on apache on this
so it feels like i should be in a safe enviroment here..
Have you tried the same code with the prefork MPM? While I know
there are people using the other MPMs, prefork is by
her server (assuming you're using the mac like me as a dev
box for eventual install on freebsd/linux mchines)
On Dec 6, 2005, at 12:36 AM, Fredrik Lindmark wrote:
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE
VSIZE
548 httpd 73.3% 0:45.79 6291 404 26
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
548 httpd 73.3% 0:45.79 6291 404 26.5M 44.6M 32.4M 110M
547 httpd0.0% 0:00.00 1 9 231 5.81M 39.1M 708K 59.6M
This is the status aprox. 40 sec after the last page was delivered.
(i
