Linux-NAS and Windows 7 PC - Way to let NAS do the indexing job?

[Oliver]

I have found DocFetcher a few days ago, installed portable version on Windows 7 Ultimate 32 bit PC, let it index several samba shares (e.g. \192.168.1.11\Public). Indexing went fast and I am delighted about the software (was dealing with Copernic formerly).
My favourite solution would however be to run DocFetcher on the NAS (Openmediavault and Debian 7, 64 bit), because the CPU usage of index updating is too heavy for my Windows PC. Did not manage to achieve this, because relative paths are different, then. Difference is network paths by Windows on one hand and Linux mountpoint paths on another.

Could you please point me in the right direction if there is a way at all?

[Nam-Quang Tran]

Hi,

because the CPU usage of index updating is too heavy for my Windows PC.

Perhaps the high CPU usage is caused by the folder watching feature. To disable it, rebuild the index in question with the option "Watch folder for file changes" turned off.

Also, not sure if this helps, but on the DocFetcher FAQ, there's an entry "Where does DocFetcher put its index files? How can I change the location of the index files?".

Best regards
q:-) <= Quang

[Oliver]

Quang,

Thanks a lot for the idea. I just tried it. Actually I removed the built indexes (after doing a backup copy) and newly built one related to the most complex share (ca. 40,000 files). Following your advise I unchecked the box for folder watching. Then, I started DocFechter.exe --update-indexes via cli and unfortunately the cpu usage went also high. Good News is that the cpu usage is below the 90 to 100 % range. Thus, it is just not recommended to run other applications at the same time. A solution for me will probably be to let the PC wake up by night and do the indexes updating job. Once a week should do, anyway.

To find a direct solution would IMO require something like having the possibility to set a string or several ones which give flexiblity to define the paths for different environments. But I am totally uncertain if this would give benefit for so many people that is was worth the effort.

[Oliver]

Finally I set it up as follows:
- PC prepared for WOL
- NAS wakes up via rtc every night anyhow due to backup jobs, downloading podcasts, etc.
- Once a week during nightly wake up time of NAS scheduled cronjob with small script to
wake up PC
- Few minutes after wake up of the PC starting script which does the indexes updates and
shuts down the PC

I would like to mention that the CPU load I discribed has NOT to be seen as a weak of the script. The script runs very well. It is more a weakness on my hardware side as I have a low capable CPU at work.

Thank you, Quang.

Cheers, Oliver

[Oliver]

Finally I set it up as follows:
- PC prepared for WOL
- NAS wakes up via rtc every night anyhow due to backup jobs, downloading podcasts, etc.
- Once a week during nightly wake up time of NAS scheduled cronjob with small script to
wake up PC
- Few minutes after wake up of the PC starting script which does the indexes updates and
shuts down the PC

I would like to mention that the CPU load I discribed has NOT to be seen as a weak of the script. The script runs very well. It is more a weakness on my hardware side as I have a low capable CPU at work.

Thank you, Quang.

Cheers, Oliver