Why are MD and RD so slow?

[vefatica]

More than 1 second each.

t:\> timer /q & do i=1 to 100 ( md dir%i ) & timer
Timer 1 off: 12:20:29  Elapsed: 0:01:59.746

t:\> timer /q & do i=1 to 100 ( rd /q dir%i ) & timer
Timer 1 off: 12:23:20  Elapsed: 0:01:57.780

IIRC, I asked this before (can't find it), it had something to do with SH* functions, and there was a way around it.

 

[Charles Dye]

Monster JPSTREE.IDX, maybe? Does adding /N to MD / RD help?

 

[vefatica]

Monster JPSTREE.IDX, maybe? Does adding /N to MD / RD help?

Yup. It makes both instantaneous.

I have Extended directory search level at 0. Can it be more thoroughly disabled?

 

[vefatica]

Monster? 27MB!!!

 

[MGibs]

Yup. It makes both instantaneous.

I have Extended directory search level at 0. Can it be more thoroughly disabled?

I had written a longer reply and then read some more.

If I'm interpreting the help correctly it looks like MD and RD will always update the JPSTree.idx file, regardless of the setting for Extended Directory search. Unless you explicitly tell them not to with the /N option.

I don't have a JPSTree.idx file, so I'm not able to test what amount of time using it adds to commands on my system.

 

[vefatica]

If I'm interpreting the help correctly it looks like MD and RD will always update the JPSTree.idx file, regardless of the setting for Extended Directory search. Unless you explicitly tell them not to with the /N option.

I don't have a JPSTree.idx file, so I'm not able to test what amount of time using it adds to commands on my system.

If you're right I'd expect JPSTree.idx to be created in the default place.

 

[vefatica]

From Rex, 6 years ago: Disable extended directory searches (completely)?