perf(java): bind ipc debug log to config, use sonic for protocol json#193
Merged
Conversation
The Java IPC protocol unconditionally enabled debug logging on the reader and writer, causing each of the ~2.5k messages per parse to trigger a full JSON dump to stderr. Bind SetDebug to the existing JavaParserServer config so debug output is off by default. Switch the protocol layer to sonic for the four Unmarshal sites and one Marshal site. encoding/json was the dominant cost on the Go side (38% of CPU, 2s of unmarshal time on a 2k-class repo); sonic cuts the ReadMessage path by ~75%. Combined effect on travel-business (2153 java files): wall 61.0s -> 53.4s (-12.5%) user 6:37 -> 5:30 Go CPU 8.48% -> 5.83%
wzekin
force-pushed
the
perf/java-ipc-debug-and-sonic
branch
from
20bcf81 to
f003066
Compare
Duslia
approved these changes
May 14, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What type of PR is this?
perf
Check the PR title.
(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).
en:
The Java IPC protocol unconditionally enabled debug logging on the
reader and writer, causing each of the ~2.5k messages per parse to
trigger a full JSON dump to stderr. Bind SetDebug to the existing
JavaParserServer config so debug output is off by default.
Switch the protocol layer to sonic for the four Unmarshal sites and
one Marshal site. encoding/json was the dominant cost on the Go side
(38% of CPU, 2s of unmarshal time on a 2k-class repo); sonic cuts the
ReadMessage path by ~75%.
Combined effect on travel-business (2153 java files):
wall 61.0s -> 53.4s (-12.5%)
user 6:37 -> 5:30
Go CPU 8.48% -> 5.83%
zh(optional):
(Optional) Which issue(s) this PR fixes:
(optional) The PR that updates user documentation: