My favorite progress bars also have the optional "Details" feed that prints what's been happening. Seeing a lot of text print really quickly gives a satisfying indicator that "things are happening!",(reply>), @ABaumstumpf 1 or 2 lines a second usually doesn't slow things down, but things change if you're using a Windows console with the default non-accelerated driver, as if you're in Safe Mode. Scrolling messages take maybe a third of a second on my i3 laptop. On a better computer it will obviously be faster but continuous output (like one line per file) will really slow things down.,(reply>), @Pacífico It also will depend a lot on what system resource your task is bounded by. The difference will be a lot more noticeable if the task is actually a multithreaded CPU-bound task, if it's I/O bound not so much especially on a modern hyperthreaded CPU as the display thread can be swapped in when the worker thread(s) go into IOWAIT.,(reply>), @Ezequiel Ciamparella Rate limiting is a great solution!<br>As for filler messages, in my experience it doesn't improve performance in any measurable way. It's worth it to build meaningful messages. Of course, just don't go overboard with it.,(reply>), @I WANT ŞĘX !!! SEE MY VÌDEÓ bad bot, be gone,(reply>), That's why I love using Linux (GNU/Linux)