On Mon, 30 Apr 2001, Gilles Detillieux wrote:
> Date: Mon, 30 Apr 2001 15:03:30 -0500 (CDT)
> From: Gilles Detillieux <[EMAIL PROTECTED]>
> To: Alexander Cohen <[EMAIL PROTECTED]>
> Cc: Joe R. Jah <[EMAIL PROTECTED]>,
Geoff Hutchison <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
> Subject: Re: [htdig-dev] Current Status as of snapshot 3.2.0b4-040801
>
> According to Alexander Cohen:
> > > With different versions of htdig:
> > >
> > > 3.1.5 11 Minutes
> > > 3.2.0b3 9 1/2 hours
> > > 3.2.0b4-031201 29 hours and 20 minutes
> > > 3.2.0b4-040801 > 12 days
> >
> > Is it just me or there a pattern developing here? ;]
>
> There sure seems to be, but we're nowhere closer to knowing why this is
> happening. It doesn't seem to be an issue with any systems other than
> BSDI. Some profiling, to know where htdig is spending its time, could be
> quite helpful. Joe, is there any possibility you could figure out how to
> compile the code on your system with profiling enabled, to get some stats
> on this?
OK, I compiled htdig-3.2.0b3 with profiling enabled and randig. Here are
the stats:
___________________________________________________
htdig: Start Digging: Mon May 7 08:56:50 PDT 2001
htpurge: Start Purging: Mon May 7 09:57:16 PDT 2001
htmerge: Start Merging: Mon May 7 09:58:09 PDT 2001
rundig: End time: Mon May 7 09:58:10 PDT 2001
HTTP statistics
===============
Persistent connections : Yes
HEAD call before GET : No
Connections opened : 2
Connections closed : 1
Changes of server : 0
HTTP Requests : 270
HTTP KBytes requested : 3034.03
HTTP Average request time : 0.0259259 secs
HTTP Average speed : 433.433 KBytes/secs
___________________________________________________
And attached is the gziped profile created by gprof.
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah [EMAIL PROTECTED]
gmon.out.gz
