feat(amazonq): Automatically pause and resume @workspace indexing when OS CPU load is high #4952
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Types of changes
Description
If the customer machine is under heavy CPU load, the
@workspaceindexing can cause slowness.When the user's OS is under heavy load, we pause the
@workspaceindexing and resumes when it is low. This is to avoid slowing down customer's device. If the customer opened multiple intelliJ instances at the same time while all these instances somehow starts vector indexing at the same time, then only the first 1 or 2 instances will get the CPU resource allocation while the others keeps waiting until the CPU load is down to a reasonable rateChecklist
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.