Subject: Re: [htdig] httpd Internal Server Error
From: Greg Lepore (firstname.lastname@example.org)
Date: Thu Jul 13 2000 - 05:34:06 PDT
I need to work on my powers of estimation, the actual command line time
for a search that returns all pages (112,000) is around 20-25 seconds. At
the time of the tests, there was only one install of HTDIG and therefore
only one database and conf file. No unusual input parameters, basically
"search everything" with the defaults. I am trying to install 3.2b2 but the
dig time is outrageous, still running after 16 hours versus 5 hours for a
complete dig with 3.1.3.
However, searches that return 20,000 hits and over are still giving the
crash. I was hoping that upgrading would give me some speed benefits. Of
course, I will also install another 128MB of RAM and cross my fingers...
At 11:35 AM 7/12/00 , Gilles Detillieux wrote:
>According to Greg Lepore:
>> Question: Should sending the results from HTDIG to Apache be taking
>> several minutes longer than the search itself at the command line?
>All other things being equal, no it shouldn't. Are you absolutely certain
>you're using the same config file and database in both instances? Is there
>anything unusual in your search form in terms of input parameters that you
>don't use on the command line?
>Gilles R. Detillieux E-mail: <email@example.com>
>Spinal Cord Research Centre WWW:
>Dept. Physiology, U. of Manitoba Phone: (204)789-3766
>Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
Maryland Electronic Capital Webmaster
To unsubscribe from the htdig mailing list, send a message to
You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Thu Jul 13 2000 - 02:52:37 PDT