1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

mkdir and rmdir very slow

Discussion in 'Support' started by Avi Shmidman, Mar 4, 2012.

  1. Avi Shmidman

    Joined:
    Feb 23, 2012
    Messages:
    238
    Likes Received:
    3
    I find that mkdir and rmdir run very slowly within TCC. They take 2-3 second each to complete, both on my main computer (core i7), as well as on my laptop (Atom). On both computers, mkdir/rmdir in cmd.exe responds instantaneously. What am I doing wrong?
    [I would add that this delay occurs even when directories are deleted within other commands, without an explicit rmdir. For instance, when I run "move /sx *.*", which deletes the subdirectories underneath the current directory after copying the files, it also pauses for several seconds while deleting each subdirectory]
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    Try them with the /Nt option.

    If you have a very large jpstree.idx file, MD and RD will have to do a lot of work to update it. If your MD / RD are fast with the /Nt option, you could either alias MD and RD to use /Nt, or trim your jpstree.idx file to only include the drives & directories you actually want to access with fuzzy directory searches.
     
  3. Avi Shmidman

    Joined:
    Feb 23, 2012
    Messages:
    238
    Likes Received:
    3
    Hi Rex,
    Yes, that was it, when using the /Nt option it executed instantaneously. Although I really enjoy the luxury of the jpstree.idx fuzzy search, so I'm not sure I'd want to sacrifice that. Oh well.

     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    Use the CDD /S drive and directory options to limit the 99% of the drives & directories you don't want to index and will never want to CD into.
     
  5. David Marcus

    Joined:
    Jun 4, 2008
    Messages:
    646
    Likes Received:
    1
    And the TreeExclude environment variable. If you look in your jpstree.idx file, you'll probably see all sorts of stuff you can exclude.
     
  6. thedave

    Joined:
    Nov 13, 2008
    Messages:
    254
    Likes Received:
    2
    Given how often this comes up, would it possibly make sense to include a "... updating jpstree.idx" message if the process takes more than a second or so?

    Or better yet, could the update be done in a background thread?

    I gave up on the whole concept myself due to the time required for the updates (and I found that for a limited set of directories, directory aliases with auto-complete suited me better)
     

Share This Page