cmderdev/cmder

Question: Bad performance?

daze99 opened this issue · 4 comments

Question

I am not sure if this is a cmder, a conemu or a clink issue.

When I run npm ci in my project in cmder it takes around 5 minutes to complete. Running the same command in cmd only takes 3 minutes.

Is this a known issue? Is there a way to debug this to find out what is causing the performance loss?

Checklist

  • I have read the documentation and made sure what I'm looking for isn't present, or is unclear.
  • I have searched for similar issues, and either this question wasn't asked before, or I didn't find any that describe my question.

You could run %cmder_root%\vendor\init.bat in Windows Cmd.exe which would take conemu out of the mix.

There's also a way to run in the init.bat that does not load clink but I can't remember what that is right now.

Running it without conemu solves the issue. I guess I will be using Windows Terminal instead.

we have an unreleased build that includes awindows aterminal and other enhancements.

I am really looking forward to that. Keep up the good work. Thanks