How to minimize system impact while building a large index

Question

I'm currently updating a common shared drive over a corporate 1 gig fiber vpn connection from home to the file server at work. It's been running about 12 hrs at this point. It has over 14k files and is 20 gig in size. I've done this before with no problems and was able to continue to use my laptop but this update using newly installed FLP 8.2, build 2751 has used up all available free memory (8G) and has slowed down my laptop to the point that it's unusable for anything else.

What has changed to create such an impact on performance and can I change some parameters to prevent that in the future?

Thank you

Answer 1

Originally FileLocator Pro indexed files using a single thread, which although slower did reduce the demands on the system for large indexes. The number of threads can be customised in the Threads/Priority Settings, so to restore the indexing threads to the original settings try switching the threads from Medium to Low:

Comments

Thanks for the answer.  I'm locked on FLP 8.2, build 2751 because that is the "corporate approved" version.  I don't see an option to set indexing threads like you have here.  Only Search Threads. I set search threads to 2 and just indexing my local "My Documents" has quickly used up all available memory.  Does this version have a memory leak? As I mentioned before, my laptop has 8GB RAM.

---

I think this is an issue for tech support, please contact them: support@mythicsoft.com