Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search very slow #63029

Closed
scosmaa opened this issue Nov 13, 2018 · 12 comments
Closed

Search very slow #63029

scosmaa opened this issue Nov 13, 2018 · 12 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@scosmaa
Copy link

scosmaa commented Nov 13, 2018

Issue Type: Bug

After the last update the search is very slow!

VS Code version: Code 1.29.0 (5f24c93, 2018-11-12T07:47:15.448Z)
OS version: Windows_NT x64 10.0.17763

System Info
Item Value
CPUs Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz (4 x 2394)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 7.89GB (1.03GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (13)
Extension Author (truncated) Version
path-intellisense chr 1.4.2
vscode-eslint dba 1.7.0
es7-react-js-snippets dsz 1.9.0
gitlens eam 8.5.6
vscode-npm-script eg2 0.3.5
prettier-vscode esb 1.7.2
webpack jer 2.1.0
vscode-icons rob 7.28.0
code-settings-sync Sha 3.2.0
autoimport ste 1.5.3
vscode-import-cost wix 2.9.0
JavaScriptSnippets xab 1.7.1
local-history xyz 1.7.0

(2 theme extensions excluded)

@roblourens
Copy link
Member

roblourens commented Nov 13, 2018

Can you explain the issue some more?

What are you searching? Is your workspace very large?

@roblourens roblourens added the info-needed Issue requires more information from poster label Nov 13, 2018
@csavtchenko
Copy link

I have been noticing this as well - using Ctrl + P - seems to do a deeper search than a simple file fuzzy search. Perhaps I have a bad cache or something? I googled a bit but couldn't come up with a solution.

This is for C++ files on a fairly large code base.

@csavtchenko
Copy link

I'll be happy to provide an info you need, except the code base :)

@roblourens
Copy link
Member

roblourens commented Nov 13, 2018

ctrl+p should just be searching files, unless you have search.quickOpen.includeSymbols enabled. There is no cache. @csavtchenko are you on 1.29?

@csavtchenko
Copy link

Okay that's good to know - definitely not enabled - definitely very slow. FZF is same speed as before so I'm slightly hesitant that it could be a HW issue.

@roblourens
Copy link
Member

What is FZF? Can you explain the problem some more? Are you on 1.29? Is it slower than 1.28 or just slow in general?

@csavtchenko
Copy link

csavtchenko commented Nov 13, 2018

FZF is a linux tool for fuzzy search. It's very fast - I use it when I'm using vim instead of visual studio code.

Typically, I press Ctrl + P, I start typing, files immediately appear as the fuzzy search narrows. However, now I press Ctrl + P I start typing - I see a "progress toolbar" then they appear. This seemed to happen on the newest update I got from the Ubuntu PPA (1.28.2). C/C++ module is 0.20.1

Sometimes the toolbar can last for a second or more. I realize that it seems short, but at the speed I need to look up different source files it has an observable effect on my speed. I'm comparing this to prior releases where this was instant.

@roblourens
Copy link
Member

1.29 just went out, can you try upgrading to that? I think it should be available for ubuntu now?

@csavtchenko
Copy link

Thank you - fixed in 1.29

@roblourens
Copy link
Member

Great, thanks.

@scosmaa more details would be great

@roblourens roblourens self-assigned this Nov 13, 2018
@scosmaa
Copy link
Author

scosmaa commented Nov 14, 2018

Sure, I'm searching using the search functionality (the project size is normal, not so big not considering node_modules folder and .history folder plugin).

I do search and it's slower than days ago using 1.28 version.

I'll do more research, I want to test if the antimalware service is responsible

@scosmaa
Copy link
Author

scosmaa commented Nov 15, 2018

Probably it was my antimalware service, I no longer have the problem, thank you!

@scosmaa scosmaa closed this as completed Nov 15, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants