"Smarter" FileCheck indexing?
Posted: Mon Nov 18, 2024 3:47 pm
It would be great if there was an option for NeoFinder to skip the recalculation of FileCheck checksums for files when updating the catalog index for a volume, only if the modification date/time of the file on disk is different from the one that NeoFinder previously stored in the catalog for that volume.
Right now, FileCheck is of limited usefulness to me because the checksums appear to recalculate every time I update the catalog for a volume, which is untenable for a large volume, like an 8 TB archive drive.
Perhaps this might be somewhat mitgated by implementing alternative, higher performance hashing algorithms like xxHash, which I previously submitted a feature request for last year? But having an option to only recalculate files with differing timestamps would be an even faster option if you dont require every file to be re-checked with eery catalog update.
Right now, FileCheck is of limited usefulness to me because the checksums appear to recalculate every time I update the catalog for a volume, which is untenable for a large volume, like an 8 TB archive drive.
Perhaps this might be somewhat mitgated by implementing alternative, higher performance hashing algorithms like xxHash, which I previously submitted a feature request for last year? But having an option to only recalculate files with differing timestamps would be an even faster option if you dont require every file to be re-checked with eery catalog update.