Rescan files everytime?!
 

Hi,

please apologize if this is obvious, but I find it puzzling (not to say annoying) that LimeWire always rescans my shared folder upon initialization. I have currently around 550 files on it, and it takes a while to complete the scan (and it takes my CPU load to 100%).

Am I doing anything wrong? Is there anyway to turn it off?

Using latest version, on Fedora Core. JDK is 1.4.2_03.

TIA

Andre

PS: I don't know if this matters, but shared folder is stored on a VFAT partition.

I have exactly the same setup as yours (java 1.4.2_03/Fedora/VFAT Shared folder/over 550 files), however I don't see the problem. What exactly do you mean by scanning?

At startup LimeWire does check the folders for new or changed files (which is very local I think), however this only takes a second on my system and happens when the system is already under stress from starting the program anyway.

If it's this you're really going to have to live with it I think, however if you're meaning that LimeWire has to calculate the checksums everytime, there's something wrong.

Hi steffanj, thks for sharing your experience.

Sorry for the partial description of the problem. Let me try to be more precise:

LimeWire does startup right away, meaning I can make a search as soon as it starts. However, it seems to rescan all the files, meaning that the file counter ("Sharing XX of YY files") goes all the way from XX=0 to XX=YY, everytime I restart LimeWire. This is what I meant by "rescans". This takes a couple of seconds (something between 30-45s) and during this process gkrellm shows my CPU at 100%.

I can live with that, and I assumed it would be checksums calculation, I just found it to be too much time/effort.

Best,

Andre

Well, I guess my LimeWire does "scan" al those files however a lot faster.

On the other hand if you're limewire is recalculating the checksums everytime it's doing that a lot faster than mine does. If i add a few files I can actually see it happen file by file and for 500+ files(depending on file size off course) that would probably take over an hour.

So I guess I can't help you. sorry.

As for the checksum recalculation, you're right: it does take a lot more than 30s to compute all the numbers -- your 1h estimate seems to be right. The <1min time was related to a partial rescan, sorry for the noise.

So, what's the trigger for this 'full rescan' to happen? New files on the directory? Also, must it really recalculate all checksums, even if only a couple of files changed? Couldn't it do it only for those files for which name/size/timestamp changed since last run?

(I don't expect you to necessarily know all these details, this is actually addressed to Limewire developers)