> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Searcher
> Sent: Thursday, November 28, 2002 6:15 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [aseek-users] Can't get a full run
> 
> 
> On Thu, 28 Nov 2002 05:53:33 +0100, [EMAIL PROTECTED] wrote:
> >Yes Mike i  run serveral aspseek servers with 2 "heavy" one's with
> >about 10.000.000 urls in it and mysql version.
> 
> Yes, that would be similar. My setup is 10028 sites/URL's. 
> 
> >all urls with status "200" are indexed and oK. you should make
> >index -D afterwards, than the deltafiles are merged and the
> >6000 urls are searchable.
> 
> The strange thing is that the database only has about 30MB of 
> data in it after 
> doing a run. That can't be right and is not since I can't find 
> anything when I 
> search after doing the index -D.

hmm file size of 30 MB, seems ok for me with 10.000 documents

> 
> >In my 8 month experience with aspseek, i can say that it is a nice
> >software, even if i would like more options in it  ;-)
> 
> Seems to be very nice but I've had nothing but problems. My very 
> first run, I 
> used the default config file which led me to 50+Gigs of data. I 
> had to finally 
> kill it and change the settings to less hops and less docs. I'm 
> now using 10 hops 
> and 5000 docs but now I can't seem to get anything anymore.

Try in another box (if you have) the default config aspseek with mysql
apache + mysql installed and fontionning
run the rbms
run service aspseek start
run index -D to great initial delta files
run index -T http://yoursite.com/
insert your urls via index -f urls.txt (it's not the right syntaxe??)
run nice -n 19 index (for 30 minutes)
run index -E
run index -D
than go to http://localhost/cgi-bin/s.cgi

You you should spend an hour or two on it.

i tried to play with compilation of the sources of aspsseek, but i 
haven't been succesfull, so i run with default config and managed aspseek.conf

maxhops 256
maxdocs -1
utf storage yes

........................

regards

gilbert

> Mike
> 
> 

Reply via email to