This isn't really possible. Vim doesn't have any concept of isolation, everything lives in a big, happy, single-threaded process, and resources are democratically shared among all plugins. The best you can do is enable profiling (see :help profiling ) and see which functions take the most time to run, but that won't tell you much about either CPU or memory use.

You might consider asking the neovim people though, they might have pondered about these issues.