Greetings Philippe, If TMPDIR is not set then htfuzzy uses /tmp, but that shouldn't slow down indexing. If you don't have /var/tmp or /usr/tmp then the database section of the code may automatically generate files in /tmp. (I'm not sure if it does, but there is a routine which checks which temp directory to use...)
Out of interest, how fast is 3.2.0b5 if you disable compression? Is it still much slower than 3.2.0b2? Cheers, Lachlan On Fri, 12 Mar 2004 01:20, Philippe Andersson wrote: > 2./ 3.2.0b5 is awfully slow. > > I used to use an earlier version (3.2.0b2 ? -- not sure). That one > wasn't terribly efficient regarding diskspace usage, but at least > it could re-index my site in +/- 10 hours. Since I upgraded to > 3.2.0b5, the disk usage has gone down (which is why I upgraded in > the first place), but it now takes more than 24 hours to index the > same amount of data (roughly 4.5 Gb). > > Since this machine only has 128 MB RAM (I know !), is it possible > that htdig creates temp files in /tmp, which, under SunOS is > actually the swap, and that it causes swap starvation ? > > If so, is there a configuration item I can use to ask htdig to use > some other place than /tmp for this ? -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
