I have created Filters using Find/Advances in the Utility Panel. Those filters work well, even when the folder I choose and its subfolders contains over 70,000 files, but I do not want results to be in a Collection because I cant move the files from there and preserve folder structure.
I tried using 'Select by Pattern' > Advanced in the Edit menu, but if I select any of the filters I created, and use it on the same folder (with over 70,000 files), the program freezes and 'Not Responding' is displayed:
I tested using smaller and smaller folders, and I always get the 'Not Responding' message unless I'm working with under 10,000 files, and even then it only works some of the time.
So I tried another method: using commands. The commands do work on folders with smaller quantities of files, but, like 'Select by Pattern' > Advanced, it freezes with larger numbers of files.
Is this a bug? Is there another method I could use without the results being in a Collection?
Does Task Manager show CPU or disk usage while this is happening, or is nothing going on?
If it needs to read metadata out of 70,000 files then it may take some time to apply. (Something we could probably improve, if it's just that. I suspect it was designed before filters could do that and hasn't been revisited since then.)
Thank you but I do not believe it is the culprit. I have tried several different filters and there is no detectable difference in performance. One of the filters I tired does use an ExifTool Column.
The filter using the ExifTool column works well in the Utility Panel - Find > Advanced.
Could you make some process snapshots and send them to us? We should be able to get an idea of where it's freezing from those. Since it's taking a very long time, it might make sense to wait 15 seconds or so between making each snapshot, so we can see if it progresses from one file to another.
Here's how to make them:
With that filter, you may be able to speed things up by reversing the two lines, so it checks the file type group first, then checks the image description second. That would do the fast check first, and avoid trying to calculate the descriptions of any non-image files.
I did more testing, and things seem to work better if the metadata field I am selecting/searching is NOT displayed. However, even when it does eventually work, 'not responding' is often displayed and there is no indication that anything is happening.
I agree with the UI principal that the user should be able to see an indication that something is happening--as one does when using Find > Advanced.
The DMP files show Opus is always waiting for the ExifTool column script, which in turn is waiting on ExifTool to run and return a result.
That doesn't match the filter shown above where it was matching on the internal Image Description property, as that shouldn't involve a script column. A script and external tool being involved complicates things a lot more, but in any case the bottleneck is in waiting for the information to come back from the external tool, since that is what is running in each of the snapshots.
(The UI could definitely handle this situation better, but wasn't really designed for filtering operations which take that long to calculate.)
Leo, Thank you. I'd like to send you more dump files - this time I'll use a Filter that does not involve the ExifTool Custom Columns script, because I am getting the same results with other Filters.
Did I send you the correct information? I meant to send you only the last page of the document. The last page documents the test I did when I created the Dump files.