| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Use an explicit 512-character BufferedWriter buffer for envelope item and envelope serialization. This avoids allocating the oversized default char buffer for each short-lived serialization writer while preserving the existing OutputStreamWriter-based encoding path. Co-Authored-By: Claude <noreply@anthropic.com>
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
Baseline results on branch: perf/sdk-overhead-jvm-v2Startup times
App size
Previous results on branch: perf/sdk-overhead-jvm-writer-buffer-512Startup times
App size
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Stack (SDK Overhead reduction for JVM)
📜 Description
Set an explicit 512-character BufferedWriter buffer for envelope item and envelope serialization.
This keeps the existing OutputStreamWriter-based UTF-8 encoding path and does not introduce a custom writer implementation.
💡 Motivation and Context
This implements the safe AR-13 serialization buffer-size optimization from the SDK overhead reduction research. The JDK BufferedWriter default allocates an 8192-character buffer for each short-lived serialization writer, which is oversized for typical envelope item JSON payloads.
Using a smaller explicit buffer reduces temporary allocation overhead while preserving serialization behavior.
💚 How did you test it?
📝 Checklist
🔮 Next steps
#skip-changelog