Usage of profiler to debug Neovim performance degradations

[pidgeon777]

I have a question regarding profiler usage in Neovim.

Consider a LazyVim setup with multiple plugins installed. Initially, when Neovim starts, it's very responsive. However, after several hours of use, it noticeably slows down (for example, when moving the cursor between windows or performing filesystem operations with oil.nvim).

In such a scenario of performance degradation, I'm wondering about the effectiveness of the profiler:

1. Would enabling the profiler with dpp during the slowdown, performing some operations (like those mentioned above), and then stopping it provide useful information about the cause of the performance issues?

2. Or would I need to start the profiler immediately after Neovim's launch and stop it when the slowdown begins to occur to get meaningful results?

The key question is about the best timing and methodology for using the profiler to diagnose these gradual performance degradations.