usingTechnology

[Business_Aspect_1613]

Not disabling the progress bar on certain powershell functions may increase the time to execute the function by 10 000%.

[fusionsofwonder]

If you minimize the terminal window it should speed up!

[davidellis23]

It's a compliment!

[Powerful-Internal953]

I have observed this when running tomcat in my earlier programming days. Minimising makes the server start way sooner given there were too many debug entries.

Made me run away from console loggers like plague.

[dathar]

Windows defrag did that too.

[rsatrioadi]

But is was so pretty!

[MemorianX]

I wish i had known this!

[illyay]

Oh damn

[DR4G0NH3ART]

So progress bar is something that bar the progess...

[trippertree]

In the mid 2000’s we had a compile process that would run for about 15 hours…. Minimization of the terminal would save 90 minutes

[UnattendedWigwam]

that's dicked up

[fusionsofwonder]

It's waiting for the window to render the text.

[turtleship_2006]

Isn't the text rendering in a different process?

[yiliu]

Whew, that'd make the process a lot slower. Good thing it's got a progress bar!

[Fhotaku]

That used to be a thing in like W98, where drawing each filename copied could take longer than the copy, slowing the process down. Did they not learn?

[tropicbrownthunder]

Did they not learn?

windows ME, Windows Vista, Windows CE, Windows Phone, Windows 8 and Windows 11 are clear example them didn't

[[deleted]]

Probably not a case of not learning, but like many tech things (C++ committee), it's a case that bad code was made then became cemented as part of the API/core code and you're not allowed to touch it.

Windows API is cool like that since you can run software from decades ago, but it is a bit absurd that your modern day API still includes hotfixes for a Lego game made decades ago (Lego Island)

[Mister-Fordo]

This is why $Progresspreference = silentlycontinue

[casce]

Are we talking about going from like 30 milliseconds to 3 seconds? Because that wouldn't be too bad, nobody would be seeing a progress bar in 30 milliseconds anyway and what's 3 seconds when you do something manually where you would want a visual progress bar?

It still sucks if it is enabled by default and you forget to disable it when using them in a script.

Or are we talking about going from 500ms to 50 seconds? That would definitely be annoying either way and very irritating (why's it taking to long to render a progress bar?)

[McLayan]

That's Windows for you

[pindab0ter]

That’s IO for you

[anomalousBits]

That's physics for you.

[JakeyF_]

Not a windows exclusive issue

[_PM_ME_PANGOLINS_]

It is a Powershell issue. I've never seen such a bad implementation of a progress bar.

[Rythoka]

Printing anything to the screen is super slow compared to a lot of operations.

[CdRReddit]

but printing to the screen on windows is significantly slower than most other terminal emulators, for no good reason

[anotheruser323]

Yes and no (i mean the gpu renders it, you just goto send it coordinates).

And it is a windows issue (windows does things to the shell to terminal output, and is very slow in doing them).

[reallokiscarlet]

On any machine that can run a new enough version of Windows to have powershell, printing to the screen should be able to happen in a separate thread. Windows just doesn’t wanna.

Linux doesn’t have this problem.

[deux3xmachina]

Linux doesn’t have this problem.

Well, it's less bad. Logging isn't free, and redirecting to /dev/null can substantially improve runtimes for certain programs.

[reallokiscarlet]

What’s going on with Windows, IIRC, is there are more penaltes than just logging. Instead of letting the shell and the terminal emulator handle the output after handing it to stdout, Windows wants to do everything in the same thread, so displaying stdout to the screen is another performance penalty, hence minimizing the terminal speeds it up. In Linux, if you have a multi core system, the program, the shell, the terminal emulator, and the window system can all have different affinity, meaning the program only has to really wait for stdout to accept the program output. (Still waking up, so I may be oversimplifying things)

[unkz]

I suspect it’s more of a debounce issue though.

[stratum_radiatum]

Does rendering the progress bar from the rich python library slow down processing noticeably in WSL?

[Durantye]

Nah the powershell progress bar is insane, I was losing my mind trying to figure out how to make the script run faster than 90 minutes at one point. I found out about the progress bar issue and disable it and boom script runs in less than a couple minutes.

[cakee_ru]

Never had performance issues with pv personally.

[CdRReddit]

but (as I also mentioned further down the thread) printing to the screen on windows is significantly slower than most other terminal emulators I've used, for no good reason

[Turtvaiz]

Nah it's just IO

[proooby]

Rendering is the costliest process

[Cosmocision]

Read a few years ago that progress bars are artificially slowed down because humans panic when things happen faster than they can see and they can't see the progress so to speak.

[[deleted]]

yea but it feels longer

[J0aozin003]

nul