I'm sure there's a better way to do it, but I'd add
a "Debug" directive for the module, then throw in some
error log calls recording time() if debug is set. Then
you know which part of the code is taking a long time.
Something very roughly like:
if (cfg->debug) {
ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r,
"time is %i", (int) time());
}
--
Ray B. Morris
[EMAIL PROTECTED]
Strongbox - The next generation in site security:
On 03/28/2008 02:50:48 PM, Michael Thomas wrote:
> Sam Carleton wrote:
> > Folks,
> >
> > Part of my web application contains an Apache C Module, mostly it
> is
> a
> > handler to control access and to serve up images, but another part
> of
> > it does access a SQLite database, which isn't called a whole lot.
> On
> > my development machine which is a 2.8GHz P IV, the module serves up
> 12
> > images very quickly. One of my customers is reporting that it is
> > taking 45 seconds on a Duo Core 1.8GHz machine! If is wasn't for
> the
> > fact that my customer is 15 hours away, I would go check it out in
> > person. Such as life.
> >
> > Does anyone have any thoughts on how I can trouble shoot this
> > remotely? I can compile and send new code to the customer, I just
> > don't know exactly what I might do to collect data.
> >
>
> Get them to look at what memory/cpu allocation running at on their
> box?
> Can they run a test from the box itself (ie. eliminate the network as
> a
> possibility)
> > Sam
> >
>
>
