Output is very slow

[patricksnape]

Couldn't find an appropriate issue for this, but output in cmder seems to be very slow. This is particularly evident when there is a lot of output produced. For example, if I'm using Python and I run a large suite of tests, a lot of output is printed. If I run this in Powershell, it flies through the output and is finished in a couple of seconds. In cmder, however, it takes many seconds and although I can tell the tests are finished, it just seems to be taking a long time to clear the output.

Any clues as to what settings might effect this/if this seems to be a bug?

[Jackbennett]

£10 says it's clink. What if you run you python from a cmd.exe instance inside cmder.

So Cmder>cmd.exe*>python ...

*At this point the lambda should go missing and {{lamb}} should be shown. I think this mean clink isn't loaded in this process.

[patricksnape]

The output is still incredibly slow after I tried what you suggested 😕

[MartiUK]

@patricksnape What happenes when you run the tasks through a standard cmd.exe? or even running powershell in cmder?

[lennartjuette]

Any news on this? I seem to have the same problems.

I have an application server throwing exceptions at me. In cmd.exe the text is barely readable. In cmder>cmd.exe i can almost trace the steps and read the causes.

Anythin i can contribute to find the problem?

[aruizca]

+1

[mmagnuski]

I have the same problem - all commands are significantly slower than normal cmd (sometimes take a few seconds). 😢

[Kyle-Falconer]

+1 the output is noticeably slow, even from a fresh download and just running the ls or ls -lh commands straight out of the box. Native commands seem to be reasonably fast (compare dir with ls).

[ghost]

I can verify this as well. I have downloaded cmder yesterday and ls is noticeably slower than when I execute it from cmd. Also, native commands like dir run much faster than say ls.

[igorng]

+1. I noticed that after re-installing cmder, everything went back to the normal, but after a few days of use it becomes slow again!

[vrajanap]

+1. Right after starting cmder with a fresh install, running "ls" took around 10-14 seconds. dir in the same console took less than few milliseconds.

[ayoubfaouzi]

The same here, just ls output is significantly slow !

[duckie]

+1 Same here. On Windows 10 Pro 64bits.

[MrWharfsnort]

I seem to be having the same problem, but only when working within a git repo

[tribet84]

+1

[flyingduck92]

+1

[delscorcho]

I followed the advice on another thread and changed cmder.lua to return false in get_git_dir.

local function get_git_dir(path)
return false
--return get_dir_contains(path, '.git')
end

Native commands are still far faster (dir vs. ls), but at least it isn't slow just to type characters in cmder.

[gabrielbiga]

+1

[bederp]

+1 the trick with get_git_dir fixed it for me.