Of course Mike there are many factors involved here. One of the biggest is of course your available resources. If you have a frame relay for example that is maxed at 512kbps and only guaranteed 256kbps, then the speed will be limited to this. I can tell you I have aspseek running on a dedicated point-to-point T-1 and I'm able to index approximately one million URLs a day many of which are on different servers. Aspseek.conf is basically set at the default settings.

My problem was not the speed of index, but more a problem with index using all available incoming bandwidth even after setting the "MaxBandwidth" directive in aspseek. Even setting this at 50% of the total bandwidth I have available, index will still consume the entire 1.544MB.

So the speed all has to do with the resources you have available to you more than how fast is aspseek's index is. Your hardware and OS will also affect the speed of indexing. If you are using an external DNS server then this will certainly slow things down. From your previous post saying it was running for days at a time for only 10,000+ URLs sounds like your resources are limited.

Regards,
Karen


>>I'm indexing 10028 URL's with a pretty basic configuration this
>
>You haven't specified how many different sites do you index?

10028 sites, or, URL's :).

Mike

_________________________________________________________________
Get faster connections�-- switch to�MSN Internet Access! http://resourcecenter.msn.com/access/plans/default.asp

Reply via email to