dotnet: cdk takes long time to execute

How long is ‘long’/how slow is ‘slow’?

PS E:\tmp> cdk init --language dotnet
PS E:\tmp> dotnet build src
...
Time Elapsed 00:00:02.05

PS E:\tmp> $sw = [Diagnostics.Stopwatch]::StartNew()
PS E:\tmp> cdk ls
PS E:\tmp> $sw.Stop();
PS E:\tmp> $sw.Elapsed.Seconds
43

In my case it takes around 40 seconds for cdk to execute the ls command in Windows. In comparison, dotnet build takes about 2 seconds.

In a docker container cdk ls takes about 30 seconds (Dockerfile)

root@1840d1c48712:/tmp/cdk# time cdk ls
hello-cdk-1
hello-cdk-2

real    0m27.063s
user    0m12.470s
sys     0m6.060s

Is there any work in the backlog to improve cdk execution time?

[unicomp21]

I was running within the “linux on windows” subsystem. Just realized it’s the antimalware service on windows. Disabling it helps a “lot”.

[eladb]

We need to do some profiling for .net to understand what’s going on. The next release should improve things slightly (x2) as we have changed the protocol between the toolkit and the app to only require a single invocation of the app once in the regular case, but it still feels like there is room for improvement.