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

Zowe Explorer causes a lot of rg.exe processes in the background #2463

Closed
zFernand0 opened this issue Sep 14, 2023 · 2 comments
Closed

Zowe Explorer causes a lot of rg.exe processes in the background #2463

zFernand0 opened this issue Sep 14, 2023 · 2 comments
Assignees
Labels
bug Something isn't working priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases

Comments

@zFernand0
Copy link
Member

Describe the bug

rg.exe (a.k.a. ripgrep) is a text searching used by VSCode. It's great for searching configuration related to Zowe Explorer in the settings.json file. However, we might be overdoing it a bit.
Things might get better with the migration to LocalStorage (see #2281 and #2304), but until then, ZE might be causing some slowness on people's machines since it locks up the terminal for a few moments. From personal experience, it can cause close to a 2-3 minute delay for a command that takes often takes less than 10 seconds to run.

C:\USER\GitHub\zowe\zowe-cli\packages\imperative\web-help>t npm run build

time 0:2:52.65 (172.65s total)

To Reproduce

Perform any of the following actions on ZE:

  • When the extension activates (we standardize settings)
  • > Zowe Explorer: Refresh Zowe Explorer (same as above)
  • Delete/Hide/Add profiles
  • Doing a Search/Filter on datasets, USS, Jobs
  • Basically anything that will touch your settings.json file

Expected behavior

  1. Either reduce the amount of settings access and modification by caching all updates and doing them on deactivation, OR
  2. Leverage the LocalStorage capabilities as soon as practicable (assuming it's more efficient) 😋

Screenshots

image

FYI, this is what it looks like with our first vNext pre-release
image

Desktop (please complete the following information):

  • OS: Windows 10
  • Zowe Explorer Version: 2.11 (coming-soon)
  • (Optional) Zowe CLI Version: N/A
  • (Optional) Are you using Secure Credential Store? N/A

Additional context

Link to similar issue:

@zFernand0 zFernand0 added the bug Something isn't working label Sep 14, 2023
@github-actions
Copy link

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

@adam-wolfe adam-wolfe added priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases labels Sep 19, 2023
@JillieBeanSim JillieBeanSim mentioned this issue Sep 25, 2023
31 tasks
@t1m0thyj t1m0thyj moved this from New Issues to High Priority in Zowe Explorer for VS Code Dec 26, 2023
@zFernand0
Copy link
Member Author

After testing all permutations of the following items, I can safely say that this issue is no longer reproducible.

  • VS Code: From 1.79.2 (May 2023), to 1.86.2 (January 2024)
  • Zowe Explorer: From 2.10.0 (first version after Keytar replacement), to 2.14.1 (most recent) & v3.0.0-next.202402142205

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-high Production outage - this quarter or at least next quarter severity-high Bug for which there may be workaround but limits the usage of the Zowe for major use cases
Projects
None yet
Development

No branches or pull requests

2 participants