Additional info:
Htdig is running like a mad dog after the document is received.
I can't find a network connection with netstat corresponding
to the retrieval of that document, so it isn't the web server.
Strange thing is: URLs pointing to other servers are htdig'd
with not slowing down, allthough they are on the same pool
of servers....
On Tue, 21 Sep 1999, J. op den Brouw wrote:
> Hi all,
>
> running 3.1.2 on slowlaris 2.5.1 and indexing our school web sites
> (about 6 servers).
>
> When indexing, around 7400 documents retrieved, htdig becomes *very*
> slow. It runs with 100% CPU time, but almost nothing happens.
> It only occurs when retrieving from one server; when retrieving from
> another servers (in the pool of servers), it speeds up again.
> This one server is the server with the most documents.
>
> PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
> 6439 msql -25 0 50M 11M run 35:09 99.10% 97.43% htdig
>
> The size is big, round 50M (11M res).
> Any hints?
>
> By the way, retrieving with a separate htdig + conf file, only digging
> the "slow" files, works perfect, no slowdown.
--jesse
--------------------------------------------------------------------
J. op den Brouw Johanna Westerdijkplein 75
Haagse Hogeschool 2521 EN DEN HAAG
Sector Techniek Netherlands
Afdeling Elektrotechniek +31 70 4458936
-------------------- [EMAIL PROTECTED] --------------------
Linux - because reboots are for hardware changes
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
