Nope. Have you ran the profiler?

tell me how to do that again

1. M-x profiler-start , choose cpu 2. scroll up and down for a while 3. M-x profiler-stop 4. M-x profiler-report

Looks ok to me too

you can use tab to expand those + to see the call stack and maybe identify some lsp-* taking a large %

I don't see any lsp- thing in there

just for reference here's what it looks on my machine running on WSL (sure, comparing different emacs setups is pointless but still)

Maybe start with wiping all emacs caches and built stuff? I've found that can sometimes "fix" mysteries.

yeah, I wiped my .elc files and the entire elpa dir a few times already

I'd try expanding that command-execute branch and see what's eating up the cpu there

ido-completing-read looks suspicious

yeah

do you have ido-mode enabled on that buffer?

https://github.com/DarwinAwardWinner/ido-completing-read-plus/blob/5995b4605b4f2d568489491704ef21bc49ddecd5/ido-completing-read%2B.el#L834 I think it comes from here, perhaps?

disabling ido-mode doesn't make a difference

try a new profilling without ido, that function should not be in the profile now

or expand the tree further, as those ido functions seem to just add advice wrappers which show up in the call stack when running interactive commands

iow. check if you can expand that #<compiled 0xbf...> node and see whats under it

it's still there but perhaps it is because I do M-x profiler-stop ?

yeah, that's possible. I've bound the profiler functions to F9-F11 to work around that

ok binding to those hotkeys helped. here's the new result

not much to see

at least some of that stuff seems to related to updating the mode line, perhaps try if something like (setq lsp-modeline-code-actions-enable nil) has any effect? (https://emacs-lsp.github.io/lsp-mode/tutorials/how-to-turn-off/)

let me put it like this. go to a reasonably dense clojure file. move up and down with cursor. switch to text-mode. do you feel the difference?

setq didn't help

I enabled some lsp(-ui) settings (`lsp-headerline-breadcrumb-enable`, lsp-modeline-code-actions-enable, lsp-ui-sideline-*) (I've normally disabled most of the UI stuff) and set lsp-idle-delay from 0.5 to 0.01 -> scrolling up and down still feels fast but I get a similarish profiler report as you (especially that compiled -> mapc -> compiled -> lsp--parser-on-message -tree). My cpu usage on a couple of cores goes up, but the same happens on text-mode :man-shrugging:

it could also be that I'm simply hitting memory limits, while working on an application on a 16gb machine

time to rename emacs to sgacs 🙂

I'm afraid this reference is lost on me

emacs = eight megabytes and constantly swapping -> sixteen gigabytes and constantly swapping

;)

it seems to be proportional to the length of the file I'm in

I downloaded emacs-mac again via brew install --cask and the problem vanished. Note to self: don't use emacsforosx again

It's no fun when you dread using your clojure development environment because of an issue like this

You must have been operating below 10 borks, when you usually hover at around 10000. Glad you are back in borkness!

well, I was away for a vacation anyway, but I dreaded going back to that slow editor...

clj-kondo has nothing with format, format is a cljfmt feature that we use, so you want to change the :cljfmt setting in a .lsp/config.edn