https://bugs.kde.org/show_bug.cgi?id=379219
--- Comment #18 from Milian Wolff <m...@milianw.de> --- @mrnuke: how long does `git status --porcelain -- path/to/linux` take on your machine? On mine it finishes within ~200ms, according to perf stat: Performance counter stats for 'git status --porcelain -- .' (5 runs): 268.574322 task-clock (msec) # 1.822 CPUs utilized ( +- 20.51% ) 101 context-switches # 0.375 K/sec ( +- 37.75% ) 17 cpu-migrations # 0.063 K/sec ( +- 22.93% ) 3,723 page-faults # 0.014 M/sec ( +- 0.07% ) 985,826,062 cycles # 3.671 GHz ( +- 20.79% ) 724,647,803 instructions # 0.74 insn per cycle ( +- 13.41% ) 136,599,722 branches # 508.611 M/sec ( +- 14.38% ) 1,823,707 branch-misses # 1.34% of all branches ( +- 13.35% ) 0.147384364 seconds time elapsed ( +- 18.04% ) What kind of disk and filesystem are you using? Maybe not yet upgraded to SSD? Note that I actually spent quite some time working on perf from within KDevelop recently, and I never saw this issue crop up. I do use git more or less exclusively from the command line, kdevelop only tracks the edit status every now and then - but so far I never noticed this issue at all. -- You are receiving this mail because: You are watching all bug changes.