is lazy.nvim faster than packer?

[siduck]

my config used to take around 15-18 ms ( packer ) before and now it takes 22-24 ms with lazy.nvim ( tested with --startuptime )

the startuptime shows different with "Lazy profile" tho! its less and i read that its more accurate than --startuptime flag

but if this is the case then is it possible to benchmark both the configs ( one with packer & other with lazy.nvim ) and without using "lazy profile"?

[yutkat]

I have over 180 plugins installed and I'm optimizing with a lazy process.
lazy.nvim is a bit faster than packer.nvim in my environment.

Here's my startuptime results and my config.

results

• packer: 30 [ms] https://twitter.com/yutkat/status/1606587331326414848?s=20
• lazy: 26 [ms] https://twitter.com/yutkat/status/1609466444152205312?s=20
  (Sorry for my Japanese tweets.)

config

• packer: https://github.com/yutkat/dotfiles/blob/43.202/.config/nvim/lua/rc/pluginlist.lua
• lazy: https://github.com/yutkat/dotfiles/blob/9f4051496a3c26ee5e782cb38b34150da9f7bcc2/.config/nvim/lua/rc/pluginlist.lua

[siduck]

@yutkat how did you benchmark both the configs? with --startuptime?

[yutkat]

Yep, I am using this function to benchmark.
https://github.com/yutkat/dotfiles/blob/9f4051496a3c26ee5e782cb38b34150da9f7bcc2/.config/zsh/rc/function.zsh#L521-L535

[yutkat]

Honestly, my personal opinion is that there is no difference in startup speed when both package managers are properly optimized.

I use lazy.nvim now because I don't like Neovim builtin package manager and lazy's UI is cool.

[folke]

Like @yutkat says, the difference would be minimal for properly optimized configs. My own config went from about 18ms with Packer to 12ms with lazy.

Slower configs do notice a big difference sometimes 100ms faster with Lazy.

Once you switched your config, it's best to delete lazy's cache one time and then restart NEovim before measuring again, since the cache probably will contain a lot of stuff that is no longer needed during startup from when you were impementing lazy. The cache file is located under ~/.cache/nvim/lazy/cache.

The startuptime you see inside lazy is the actual CPU time of the Neovim process till UIEnter, on Linux and Macos. Not on Windows.

[siduck]

@yutkat another doubt, whenever i install new plugins lazy.nvim uses some custom theme and disables my statusline too :(

[siduck]

@yutkat i dont use any colorscheme plugin, i have my own which just generates a file which contains multiple set_hl api function, so it compiles all the computation stuff into cache and i load my file by loadfile function like

loadfile("file path")()

that sets all the hl groups etc

any idea @folke

[folke]

That is normal. Check the setting config.install.colorschem. Lazy installs missing plugins before anything else is loaded, so your own colorscheme would not have been loaded yet. You can configure a list of colorschemes that lazy will try to load before installing. If you'd start with no plugins at all, then t will default to the builtin habamax colorscheme which is far better than the default one.

[siduck]

That is normal. Check the setting config.install.colorschem. Lazy installs missing plugins before anything else is loaded, so your own colorscheme would not have been loaded yet. You can configure a list of colorschemes that lazy will try to load before installing. If you'd start with no plugins at all, then t will default to the builtin habamax colorscheme which is far better than the default one.

i have to run a file that loads some set of highlight groups, can I disable habamax and run a piece of code before?

i loaded my highlight related code in my custom plugin

and that nvchad_ui module just loads some files with 'loadfile' function

[folke]

no, you should just create a file /colors/nvchad.lua and do that require in there, like any normal colorscheme

[folke]

or add an autocmd on Colorscheme and check if habamax is set. Then load your own instead