I'm a little behind here, but this thread caught my eye:
On 5/6/07, Perrin Harkins [EMAIL PROTECTED] wrote:
On 5/6/07, James. L [EMAIL PROTECTED] wrote:
my question is
once the app produce the html, does the memory
allocated by the parsed data get released to perl?
that memory will be
My main problem is: Memory Usage.
Currently, the apache processes take (each) about 150 MB memory,
what's quite a lot. Now, i've been wondering which module and why it
takes that much memory at all.
Check out this thread:
http://aspn.activestate.com/ASPN/Mail/Message/modperl/3173671
Reviving a thread 4 months later...
On 5/10/06, Perrin Harkins [EMAIL PROTECTED] wrote:
On Wed, 2006-05-10 at 10:26 -0700, Jay Buffington wrote:
At first I was caching the database handle myself when running outside
of mod_perl. In mod_perl I was relying on Apache::DBI returning the
same
This solves a problem I was having some time ago while implementing
ecommerce (verisign):
1. insert customer's info
2. authorize credit card
3. log authorization response to database
4. if auth fails roll back #1, but keep #3
I was planning on solving this problem using Oracle's
Thank you all very much. As mentioned, this isn't a mod_perl issue.
That NLS_ variable sounded familiar. I looked in my httpd.conf and found this:
PerlSetEnv NLS_LANG american_america.we8iso8859p1
Which controls (among many other things) the default date format.
I've moved that line out of
Hi,
I'm using DBI with DBD::Oracle. I've noticed that under scripts the
default date format is mm/dd/ HH24:MI:SS, where as under mod_perl
the default returned date format is -MM-DD.
That is, if I select a date column from the database without wrapping
it in a TO_CHAR() function, I get
On Thu, 2006-06-22 at 11:20 -0700, Jay Buffington wrote:
I'm considering writing a PerlLogHandler that will print out the
memory usage (using GTop) before and after each request so I can find
the offending code path.
I wrote this script and it turned out to work very well. It's small,
so I
I want my modules to be able to get a the same database handle
anywhere they need it during a single request (if under mod_perl) or
the life time of the script they're in.
At first I was caching the database handle myself when running outside
of mod_perl. In mod_perl I was relying on
Hi,
I have a handful of fairly simple mod_perl 1 handlers that I want to
test. I've tried using Apache::FakeRequest, but its lacking in a lot
of areas.
After subclassing it I was able to write a test that looked for the
correct headers_out, but it was a pain and kind of sloppy.
Does a more
