Performance of AllDup with a large set of search results

[allduperocks]

I have been using AllDup for years and it is the best duplicate finder and manager available. With a recent version, the search result page appear hung when there are tens of thousands of groups. It's only in looking at the Task Manager that I can see that 100% of a single CPU is used by AllDup and is still working. The search result page populates eventually after many hours. Maybe there should be a message stating that the application is working? Deleting files is also much slower--several seconds to delete a single file. I think older versions of AllDup might have performed better? Will future versions take advantage of concurrency for better performance?

Thank you for the continued releases of new features and optimizations.

[Administrator]

How much memory does the AllDup process use when displaying your search result?
Please use the Windows task manager to determine the memory usage.

[allduperocks]

The AllDup process is currently using 1.276 GB when displaying the search result. This is after deleting a bunch of files.

[Administrator]

I guess the problem comes from the large memory consumption. The larger the search result, the longer it takes to carry out certain actions.
you can try to split the groups of your current search result into 2 search results for a faster workflow:

1. load the original search result
2. delete half of the groups
3. save as a new search result
4. load the original search result
5. delete the other half of the groups
4. save as a new search result
5. exit Alldup
6. load a splitted search result

[therube]

(I've posted a couple "slow" reports, so I'll just link them here for reference:

Slow with Compare Between Different Folders
Slow Deletion)