Performance Issues with PowerShell

Hello everyone!
Let me preface this by saying how much I am loving me some
Powershell...

Imagine for a moment that I would like to move to Powershell as my
single, well, shell, but I am having a serious performance issue and
want to validate if others are seeing the same.

I use a particular file share with about 5000 directories. In cmd, I
can type "dir cmd*.*" and get a directory listing instantly or I can
type "cd cmd", press Tab and immediately have the command expanded to
show the first matching directory.

Not so in Powershell, typing "dir cmd*.*" takes about a minute to
return a list of the appropriate directories. Typing "cd cmd" and
pressing Tab to expand the directory goes off into the ether with no
response.

Is this expected performance or am I just not using PowerShell as the
right tool? Should I expect to be able to use Powershell right away to
replace CMD and just keeping expanding my shell usage as I learn to
exploit Powershell?

We did very minimal perf work in V1.0. The example you sight highlights a
very specific perf issue that we expect to address in our V1.1 release.

--
Jeffrey Snover [MSFT]
Windows PowerShell Architect
Microsoft Corporation
This posting is provided "AS IS" with no warranties, no confers rights.

This is when we are suppose to ask v1.1? When is the release date?

"Jeffrey Snover [MSFT]" <jsnover@ntdev.microsoft.com> wrote in message
news:264606D5-6182-458D-A381-C375D8BF3DB4@microsoft.com...
> We did very minimal perf work in V1.0. The example you sight highlights a
> very specific perf issue that we expect to address in our V1.1 release.
>
> --
> Jeffrey Snover [MSFT]
> Windows PowerShell Architect
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, no confers rights.
>
>

On Wed, 20 Dec 2006 08:34:23 -0800, "Jeffrey Snover [MSFT]"
<jsnover@ntdev.microsoft.com> wrote:

>We did very minimal perf work in V1.0. The example you sight highlights a
>very specific perf issue that we expect to address in our V1.1 release.

Jeffrey,

You know the question that's coming. <grin/>

Have I missed something? What's going to be in the v1.1 release?

Thanks

Andrew Watt MVP

For me, typing GET-ME<tab> sometimes takes up to 10 seconds of disk churning
before it becomes GET-MEMBER.