When opening copy jobs that contain 1M+ files, Teracopy seems to hang in a ‘not responding’ state for an unpredictable amount of time, often more than 24 hours. If the app does return from the ‘not responding’ state, it will often return to that state after pressing the ‘copy’ button.
Using procmon I determined that it’s working with the ‘history’ DB files in the user’s AppData\Roaming\TeraCopy\History …. the DB files are ~2.5GB per file.
The physical server running teracopy is a 16 core/128GB server dedicated to TeraCopy.
Am I hitting a limitation of the SQLlite databases? Is there a workaround?
Please authenticate to join the conversation.
In Review
TeraCopy
2 months ago

Scott Watson
Get notified by email when there are changes.
In Review
TeraCopy
2 months ago

Scott Watson
Get notified by email when there are changes.