Hi,
tag2find itself does not scan files at the moment, it just tracks newly created files and file movements without parsing them. The performance impact should be quite low after the first initial few minutes when the tag2find service needs to list all directories on the supported disks to allow fast tracking of the files.
Do you see any performance problems after the initial phase?
Hmm, now while thinking about it, it could be that the indexing of Copernic causes a lot of file change entries in the NTFS Change Journal, so this would cause tag2find to react to this. I'll reinstall Copernic and will investigate this.
A possible solution that comes to my mind regarding this issue would be if you could specify folders where we would not even try to track files, as I expect that hardly anyone will want to tag the Copernic (or any other search engine) index.
So, thanks a lot, your feedback just gave me some new ideas what we need to improve performance
Best regards,
Martin