Add 500 ms debounce to Pylint to reduce CPU usage #89
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pylint can be very CPU intensive depending on how its configured. It's not uncommon to get fans when making rapid changes.
lithammer
commented
May 4, 2021
| @@ -472,6 +472,7 @@ export const linters = { | |||
| "pylint": { | |||
| "sourceName": "pylint", | |||
| "command": "pylint", | |||
| "debounce": 500, | |||
There was a problem hiding this comment.
I guess this number can be discussed. But the linter is relatively slow and resource hungry, so...
lithammer
changed the title
|
Thanks! it seems make sense |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pylint can be very CPU intensive depending on how its configured. It's not uncommon to get fans when making rapid changes.
Fixes GH-87