Recover C:\ causes nsrindex to run at 100% for a long time

[libove]

I had a hard drive fail, and wanted to restore the whole system from NSR backups. I installed the new hard drive, installed Windows XP again, loaded the Networker client, ran Recover, and right-clicked on C:
It took more than an hour for nothing to come back in the Recover window. It seems that I have some kind of massive inefficiency problem on the Networker server, because nsrindexd ran at ~90% CPU for that entire time.

To get a clearer picture of what was happening during that time, I killed the nwrecover off and started a recover, and typed "add C:". It began, slowly, listing out the tens of thousands of files that the whole drive would include. At the rate it was finding and listing files and directories, it would take days or longer.

I cross-checked the index for that client, which took only a minute and returned no errors. The index is only about 18MB.

Is there something I can do to make the indexes / nsrindexd more efficient?

 

[605]

This is actually true.

1. If you want to browse through a directory, do not forget that the index has be read completely.

2. There is a problem if you have a flat directory with a huge number of files.
Starting with about 40.000 files NW will slow down if it has displayed all file names.
Actually you can see this very well using the Windows GUI - even 1 Mio files is not a problem for NW,
you will see all filenames rushing through at the bottom of the window. That takes about 5 min.
Unfortunately, NW then "internally organizes itself" which will take him much longer.
On my systems I noticed a delay of about 45 minutes before he displays the file list.

To my knowledge, Legato is improving this but it will take a while.

 

[libove]

Ugh.

Thanks for confirming that it isn't just my system.
-Jay