I'm asking this question because this question Neovim takes so long to source ruby.vim have been put on hold.
Nobody said Neovim is off-topic on this site (neither the meta question about this or the current help center nor its future revision). We even have a dedicated tag with a lot of questions about Neovim.
Carpetsmoker closed the question because the performance issue didn't come from Vim itself but came from a third party tool (
rbenv) which is clearly off topic.
The vote for close was because the problem was related to ruby, not to neovim. Note, that I'd have said to run nvim with
strace and then check were the time was lost.
Now the problem could be changed into: "how could I know when my performance problem is related to vim or to an external process or device that takes to long to respond?"
I had the problem a few times because my runtime files are on an overloaded GPFS device, and that a few option like
** which triggered a lot useless calls to
stat and to