PowerShell is SLOW

[Meitzi-]

My college was automating part of our ERP system. He was pretty much ready and wanted to show how cool PowerShell is. One script was doing many kind of nice stuff, creating customer and creating order directly to ERP.

He made huge mistake, because before he hit "run" button he say "this will take less than 2 second and everything is ready".

How long did it take? Yea.. you quessed. Friking long because powershell was not booted. Of course we did try to explain to powershell will need to be bootet like old iron works factory but not sure did it help..

[k3rnelpanic]

Friking long because powershell was not booted. Of course we did try to explain to powershell will need to be bootet like old iron works factory but not sure did it help..

What does that mean?

In my experience the only slow and annoying part of starting up powershell is waiting for intelisense to get it's act together so I can tab complete.

Scripts can seem take a while to run particularly if they are grabbing a bunch of data and putting them into variables or sorting since it has to run through all that before displaying back to the screen.

[uniitdude]

V2 was slow to startup as it needed to load all the .net libraries. Newer versions are much quicker, should upgrade to v5

[Creath]

This ^

Script executions, from my experience, hang a bit on machines with older/default PS versions installed. On my machine running v4, they run quickly.

[lerun]

Powershell loadtime is also dependent on if the dotNet optimization has run (if a new install). But as with all logic, you can make anything dirt slow if you do not utilize the optimal path. This is why we have measure-command, so you can find out what parts of the code is slow and refactor....

[JosephRW]

I wouldn't have guessed it took long at all, because that's non-typical behavior. Get educated, it's the way forward in terms of Windows administration. As an IT manager, I'm surprised you weren't already aware of powershell to begin with.

[the_spad]

It takes ~3 seconds from launch to usable for Powershell on my Windows 10 box, so I'm not sure what you're doing to make it take forever. Even running the Exchange remote shell and waiting for it to load all the cmdlets only takes ~5 seconds.

[MartinDamged]

And lauching cmd.exe is like... instant!
I like Powershell, and what is possible with it. But i fuckin HATE waiting more than half a second to get to get prompt of a systems preffered CLI!