Why is powershell tab-to-autocomplete so slow?

Powershells commands are very wordy, especially compared to Linux’s shorter, often abbreviated, commands. This makes them very prone to typos since there’s more to write, so I like to use tab to make sure its spelled right. However, whenever I do this in the labs, Powershell pauses for about 10 seconds before filling in the command. Meanwhile on the Linux terminals, its very snappy and responsive with its autocomplete.

What’s the difference? Are there just that many more commands in Powershell compared to Linux, or is it a matter of how each terminal searches through its catalogue of available commands? I can’t imagine it would have to do with the number of commands since it would have to be an insane number for it to take anything longer than a brief moment to comb through using optimal techniques and modern hardware.

Its something that’s been bugging me for a bit and I just really wanna know what the root cause is/could be. I don’t use Powershell much or at all outside of the labs on here so I don’t have anything to really compare to, but if it were to take a long time on a personal computer, how could one speed it up, if possible?

Furthering the course, I now understand why it takes so long. with 13k+ cmdlets and aliases on top of that, its a lot to look up.

I still feel it could be faster, potentially at the cost of modularity, but I get it.


Inbetween writing this and doing more labs, it no longer takes 30 seconds to autocomplete anymore. I don’t know what the difference is, but I welcome it.

I will leave the thread up as a lesson in patience.