Significant lag on start

[asmallcarrot]

Issue:

After a clean install of the latest version of nvim and no other plugins when I install nvim-tree.lua it takes ~1-2 seconds for me to be able to do any actions in a document. The document renders but I can not for example move my cursor.

System info:

OS: Artix w/ openrc
Terminal: ST
Nvim Version: v0.5.0-dev+1416-gec7b21918 (I tried the AUR version and built from source)

Start time log

times in msec
 clock   self+sourced   self:  sourced script
 clock   elapsed:              other lines

000.009  000.009: --- NVIM STARTING ---
000.322  000.313: locale set
000.683  000.361: inits 1
000.698  000.014: window checked
000.702  000.004: parsing arguments
000.801  000.099: expanding arguments
000.853  000.052: inits 2
001.437  000.584: init highlight
001.438  000.001: waiting for UI
002.015  000.577: done waiting for UI
002.033  000.019: initialized screen early for UI
005.706  003.600  003.600: sourcing /home/rice/.config/nvim/init.lua
005.711  000.078: sourcing vimrc file(s)
010.559  004.828  004.828: sourcing /usr/local/share/nvim/runtime/filetype.vim
010.700  000.023  000.023: sourcing /usr/local/share/nvim/runtime/ftplugin.vim
010.843  000.020  000.020: sourcing /usr/local/share/nvim/runtime/indent.vim
011.193  000.179  000.179: sourcing /usr/local/share/nvim/runtime/syntax/syncolor.vim
011.353  000.368  000.189: sourcing /usr/local/share/nvim/runtime/syntax/synload.vim
011.411  000.456  000.088: sourcing /usr/local/share/nvim/runtime/syntax/syntax.vim
011.776  000.210  000.210: sourcing /home/rice/.config/nvim/plugin/packer_compiled.vim
012.101  000.157  000.157: sourcing /usr/local/share/nvim/runtime/plugin/gzip.vim
012.117  000.006  000.006: sourcing /usr/local/share/nvim/runtime/plugin/health.vim
012.176  000.051  000.051: sourcing /usr/local/share/nvim/runtime/plugin/man.vim
012.477  000.143  000.143: sourcing /usr/local/share/nvim/runtime/pack/dist/opt/matchit/plugin/matchit.vim
012.534  000.349  000.206: sourcing /usr/local/share/nvim/runtime/plugin/matchit.vim
012.647  000.105  000.105: sourcing /usr/local/share/nvim/runtime/plugin/matchparen.vim
012.944  000.288  000.288: sourcing /usr/local/share/nvim/runtime/plugin/netrwPlugin.vim
013.062  000.007  000.007: sourcing /home/rice/.local/share/nvim/rplugin.vim
013.067  000.105  000.099: sourcing /usr/local/share/nvim/runtime/plugin/rplugin.vim
013.146  000.069  000.069: sourcing /usr/local/share/nvim/runtime/plugin/shada.vim
013.177  000.015  000.015: sourcing /usr/local/share/nvim/runtime/plugin/spellfile.vim
013.291  000.102  000.102: sourcing /usr/local/share/nvim/runtime/plugin/tarPlugin.vim
013.368  000.062  000.062: sourcing /usr/local/share/nvim/runtime/plugin/tohtml.vim
013.392  000.011  000.011: sourcing /usr/local/share/nvim/runtime/plugin/tutor.vim
013.540  000.137  000.137: sourcing /usr/local/share/nvim/runtime/plugin/zipPlugin.vim
013.682  000.977: loading plugins
013.824  000.070  000.070: sourcing /home/rice/.local/share/nvim/site/pack/packer/start/nvim-tree.lua/plugin/tree.vim
013.949  000.196: loading packages
014.062  000.112: loading after plugins
014.077  000.015: inits 3
015.485  001.408: reading ShaDa
015.653  000.168: opening buffers
024.156  008.503: BufEnter autocommands
024.159  000.003: editing files in windows
024.208  000.050: VimEnter autocommands
024.210  000.002: UIEnter autocommands
024.211  000.001: before starting main loop
024.693  000.482: first screen update
024.695  000.002: --- NVIM STARTED ---

This log doesn't appear to show the lag

File Structure

├─ nvim/ 
│  ├─ init.lua/       
│  ├─ lua/         
│        ├─ plugins.lua/   
└─

Recreating

nvim config folder:
init.lua:

require('plugins')

lua folder:
plugins.lua:

local execute = vim.api.nvim_command
local fn = vim.fn

local install_path = fn.stdpath('data')..'/site/pack/packer/start/packer.nvim'

if fn.empty(fn.glob(install_path)) > 0 then
  fn.system({'git', 'clone', 'https://github.com/wbthomason/packer.nvim', install_path})
  execute 'packadd packer.nvim'
end

return require('packer').startup(function(use)
  -- Packer can manage itself
  use 'wbthomason/packer.nvim'
  --file managing
  use "kyazdani42/nvim-tree.lua"
  -- theme
  -- use 'shaunsingh/nord.nvim'
end)

Without Plugin

WithoutPlugin.mp4

With Plugin

WithPlugin.mp4

[hamsterBiscuit]

same as i

[asmallcarrot]

what tree are you currently using? I've been using a combination of Leexplore and telescope file search.

[kyazdani42]

cannot reproduce with the config provided, this might be related to your shell (better to set shell=/bin/bash or some fast shell with low configuration when using neovim if you want to avoid perf issues with plugins)

[gegoune]

Interesting, never thought of shell setting. Would rather want to keep my fully configured shell for terminal buffers.

Are you saying that each git command nvim-tree executes spawns full shell instance?

[asmallcarrot]

currently I'm using the dash shell for /bin/sh and zsh for my shell. I tried bash for both bin/sh and my default shell, lag still persists.

[kyazdani42]

Hum i had someone with this issue before and he had issues with fish which made the whole tree laggy. I guess when you run system for git commands, it gets slower.
What happens if you disable the git integration in the tree ? does the lag still persist ?

[kyazdani42]

i might just make the git stuff asynchronous, it might fix number of lag issues

[gegoune]

Instant tree with got status showing moments after would be absolutely fine and probably even preferable for me. Just a personal opinion.

[kyazdani42]

just implemented that in b31003e, could you guys tell me if it changes something ?

[asmallcarrot]

Still lags just as bad for me.

[gegoune]

I cannot remember now what startup time for nvim-tree was before, I am not seeing significant differences between commit above and master, but it[s starting pretty fast for me now.

[asmallcarrot]

It changed it but no where near what I would consider usable.

[kyazdani42]

@asmallcarrot could you try disabling git integration fully and tell me if the lag persist ?

[asmallcarrot]

I went through the readme and was unable to find out how to.