You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my SSD in Debian, running the script on around 2.9k files, it was done blazingly fast. On my Windows machine with a non-SSD, it took upwards to 35-40 seconds on the same fileset.
It's not a big deal since it's a one-time operation, but having some kind of progress report or verbosity to show that the script is actually working on something might be a good idea.
The simplest thing possible would be to have an increasing file counter or percentage counter running in the terminal/command prompt.
The text was updated successfully, but these errors were encountered:
On my SSD in Debian, running the script on around 2.9k files, it was done blazingly fast. On my Windows machine with a non-SSD, it took upwards to 35-40 seconds on the same fileset.
It's not a big deal since it's a one-time operation, but having some kind of progress report or verbosity to show that the script is actually working on something might be a good idea.
The simplest thing possible would be to have an increasing file counter or percentage counter running in the terminal/command prompt.
The text was updated successfully, but these errors were encountered: