Diagnosing slow api.make.build() performance about hotpot.nvim HOT 3 OPEN

Copied from discussion

Is it possible to share your whole config as a repo? Also can you confirm you see the same with nvim 0.9.4?

I would try putting some logging in hotpot/api/make.fnl, in find-compile-targets and find-clean-targets I guess, to check if its some wayward dir scanning, and also in do-compile to check if some compile is taking forever.

I have added some basic timing data to the verbose report, including each files compile time, the total compile time and the total disk searching time which might help narrow down whats going on. It would be nice to include per-glob search times too but im not 100% sure on how I want to report that right now.

You will have to pull the latest HEAD for the updated reporting, its not in a release yet.

from hotpot.nvim.

@gwerbin, I find the issues interface a bit better for this as discussions starts hiding posts when things get long.

In addition to pulling the latest head for the maybe useful report, I you could try adding a print statement after this:

to get a real view on what files hotpot is looking at, in case its running amok somehow. You should be able to just open that file up in your repo, add the print and save, then hotpot should automatically recompile (you should see a report down the bottom if it worked), then open a new nvim instance to try it out.

from hotpot.nvim.

@rktjmp as I mentioned in the discussion thread, I ended up fixing my particular issue.

That said, I think there's a case to be made for additional verbose logging of all files scanned (not just files compiled), so consider this a feature request. Could be useful in general when debugging a bundle of api.make.build patterns.

I pulled the main branch and the timing report looks great, thanks for adding that!

I'm happy to help with improving logging. How do you feel about a verbose = "debug" option?

from hotpot.nvim.