Is there a practical limit to how many pending write-backs you can have stored up? Or a downside to having 'too many'?
I currently have 20,000 files pending multiple write-backs for each and am wondering if this slows down Imatch , or if there is a line that shouldn't be crossed.
No. IMatch stores a flag for each tag, together with the data, which tells it if this tag needs to be written. IMatch also maintains a separate table for repeatable tags to keep track of tags which need to be erased completely. The amount of data is negligible.
Of course the more files you have in the database, and the more data these files have, the longer certain operations take, e.g. calculation the pending write-back collection. But that information is usually cached anyway.
Good to know. Thanks