cmder: Extremely slow startup
I’ve upgraded from version 1.3.6.678 to latest 1.3.11.843 and the startup is painfully slow. More than 5s.
I’ve even tried downloading a fresh copy of the mini release and put it into my C: drive (which is a Samsung 960 EVO) and it’s the same.
Previous version loaded almost instantly.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 7
- Comments: 27 (11 by maintainers)
Is this startup speed normal? I think it is very slow.
just remove those function calls , and hard code all env, since you know the very git_install location. My demo, https://github.com/doglex/Light_Weapon/blob/master/cmder/vendor/init.bat
which is fast 0.5s in HDD 0.1s in SSD
startup > tasks > cmd > add arg /f
for me it was the GIT_INSTALL_ROOT environment setting that was missing. therefore the init.bat was taking a long time to discover where git.exe was installed. After setting GIT_INSTALL_ROOT in my environment settings, cmder starts a whole lot faster.
Thanks fakaki, I got similar results as well by doing that recommendation.
For anyone wondering how to do it, add the line underlined in red here.
If you don’t use Git Bash that often, you can skip the whole thing after you run CMDer for the first time. Note: You can always just comment this line when you’re using bash regularily.
The hint from mvanwaaijen really helped! Before: Cmder Startup time used to be 9 seconds on a modern Windows 10 Notebook, i5, 16 GB, SSD,… After adding GIT_INSTALL_ROOT environment variable (system): < 3 seconds!
I also noticed slowness on my corporate laptop but after disconnecting the network drives i saw a huge improvement in startup time when opening new bash consoles. Hope it helps.
@eparizzi : are you a windows insider ? actually i have the same issue, and i actually wonder if its not related to windows itself… some of my programs accessible via right-click ( open with… ) are now pretty slow to launch ( eg. for IDEs or archives programs ). On the other side the cmd/powershell shift/right-click works pretty well. Also i had activated the sandbox for windows defender, disabling it reduced the launchs… ( sorry for mistakes, english not primary )
@speedysparrow do you have an antivirus/antimalware you can disable and try again. These could be slowing it down. If they are you might be able to exclude cmder from on access scans and get it back to full speed.
Just curious what hardware you running this on, processor, hdd type, and memory?
If I add
/ftocmd::Cmder task1.3.11is actually 1 second faster than1.3.6`