Performance Benchmarking

[jgollenz]

How would one go about to measure the time each plugin takes when issuing e.g. a vim movement? I get the feeling that, since the recent addition of some treesitter features, this plugin has become noticeably slower for me. What I experience is really janky movement when I spam j to move down a ~2.5k lines file with every fold closed. When the folds are open, everything is smooth. So is the general movement with minimal_init.lua. When I incrementally throw out my other plugins, it gets better, but it's hard to tell which plugins are the culprits and why.

What I'm looking for is something like vim-startuptime, but more fine-grained. Any ideas?

edit:

Ok, I tried with ba98745, which is before the treesitter features and it moves smooth. There has definitely been some performance penalty somewhere. I'll make an issue

[kristijanhusak]

Can you try on this commit 541f097 ? This is before I introduced tree-sitter for folding, maybe that's where the issue happens.

[jgollenz]

@kristijanhusak I tried 541f097, but there is no change. It got worse with 8a61c91, this much I can tell. I'm stepping backwards through the commits and will report

[jgollenz]

Ok, looks like it completely goes away for me on 88dac80

[jgollenz]

The next commit was about extmark. I do use a lot of links and have conceallevel = 2

[kristijanhusak]

Ok this is probably due to new markup highlighting.

[kristijanhusak]

You can do some performance benchmarking like this:

:profile start profile.log
:profile file *
:profile func *

Do the thing that's slow, and then:

:profile stop
:qa!

Then open up profile.log file that was created