J and T
Mon, 23 Sep 2002 20:39:48 -0700
Today I started with an empty index and inserted 175,000 URLs: ./index -i -f myurls.txt
Then I ran the indexer: ./index -N 100 -s 0 Consumed a bunch of memory once all was resolved and running. In fact I'm running 2GB DDR 200MHZ RAM on a dual 2.2GHZ Zeon box with Linux running the latest kernel. While running index it will not only consume the entire 2GB, but also about 2,000k of disk swap. Once index is complete none of the RAM was released. The only way I can get it back so other programs were not swaping memory to disk is to do a reboot. This process took 7 hours by the way. Has anyone experienced the same problem? I could easily index 1,000,000 URLs all at once using mysql and a multi-threaded perl indexer with minimum RAM consumption and when done (about 20 hours later) all RAM is released. Maybe it's because I wrote the Perl script? All other programs I have used release the RAM back, but not aspseek's indexer for some reason. Thanks! _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx