Filter out excessive logging of classfile parsing from m2e in "debug mode" #2785
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.
When having
-Djdt.ls.debug=true
set forjava.jdt.ls.vmargs
and importing a project like LemMinX, I noticed the logs would get very large. Approximately 1.5MB in size after just the initial import. I also think it's made worse by the fact that some of the log messages here, are sent on rebuild. I also believe they slow down other operations.With this change the log size for the same project goes down to 0.4MB.
Before merging I just want to play around with tallying all log messages by their originating logger. Maybe there are others worth suppressing. It's a fine line between keeping debug logging and filtering things that only worsen performance.
Update