indexing too slow and doesnt find module definitions at instances.

[JendaPov]

Hi, Im quite excited about this new extension to VS Code as it looks that it could finally support the most important stuff for (System)Verilog code. However, Im still not able to use it "fully properly", so far works well inside one module's source file.

• Im able to define a top module and see the instances inside (but only 1 level down from this top)
  I get such errors for the instances definitions (their module files)
  
• the indexing looks infinite (however, the tags in the currently opened file work well)
  I still have this cycling
  
• I turned off all linters for now, but still get these
  

Now, to improve the indexing speed I wanted to setup some white/black lists for the files where to look for them. Ideally, I would use an explicitly defined file list, which is usually loaded with an -f option to almost any EDA tool (eg a simulator), is this actually supported here?

Anyway, I tried to somehow make it faster with this setup:

"verilog.index.enableSymlinks": false,
"verilog.ctags.path": "_SOME_ABS_PATH/ctags",
"verilog.lint.slang.enabled": false,
"verilog.includeGlobs": [
"_SOME_ABS_PATH/src/*.{svh}",
"_SOME_ABS_PATH/src/auto/*.{svh}"
],
"verilog.excludeGlob": "**/{syn,lay,dv,dms}/**/*",
"verilog.moduleGlobs": [
"_SOME_ABS_PATH/src/*.{sv,v}"
]

Im limiting the verilog.includeGlobs and verilog.moduleGlobs to quite a small number of source files with these paths, but its still not ending. Are those 2 actually acting as a whitelist or the indexing may still happen somewhere else in the VS Code current workspace?

thanks and regards

[JendaPov]

update:
performance fixed by changing a general VS Code setting from default:
"search.followSymlinks": false,