I’ve removed your link to a competitor product as this is an official Piriform forum: if anyone is interested they will be able to find it easily enough.
And whilst we’re talking about the competition, that product is only 291 kb. Oh for the days when CC was well under 1 mb, long gone now. CC has always done more than file deletion, but it is a bit of a porker now (es ist ein bisschen fett).
It all depends on the mechanics of the deletion. A folder with 100,000 entries is huge, with hundreds, if not thousands, of MFT records and many index clusters. For secure deletion CC must:
Open each file
Overwrite the data
Save the file
Rename the file
Delete the file
Every time a file is renamed its position in the huge list of files in the folder is altered. Files are stored in the folder in alphabetic sequence, and when the file is renamed (to a variant of ZZZ.ZZZ) the sequence must be shuffled up or down to accommodate this. If CC overwrites, renames and deletes the files in reverse alphabetic order (last file first) then only a few MFT records have to be rewritten every time a single file is deleted. If it processes the files in a different order, or a different manner, then there’s a huge amount of work to be done.
On the other hand finding the last file in a huge folder is onerous. Every entry for each file has to be read until the EOF is found. And if the last file is edited, renamed and deleted, is position lost so that the last file has to be sought from the start again? It would be easier to delete the first file first, but the renaming would be a nightmare for performance. Is this what is happening?
We can add to all this writing entries to the log journal, updating the MFT index clusters, altering the cluster and MFT bitmaps for every file deleted, and syncing the disk every few seconds. And things I haven’t thought of.
It’s a wonder really that the process ever finishes.
I don’t know what the opposing software does, but this list (apart from the editing and renaming) is what NTFS has to do to delete files from a folder, whatever software is used. Perhaps CC doesn’t use the most efficient way of securely deleting the files, and it is only exposed on folders with a very, very large number of files.
You could be better off if you normal deleted the folder and then ran a wipe free space.
The overwriting pattern doesn’t matter by the way, it’s all randomised before being written to the disk.