POC: Improve JDBC driver performance using ByteBufferManager for TDS packet handling #2671
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.
This POC introduces a ByteBufferManager and BufferPool in the JDBC driver to optimize memory usage during TDS packet processing.
Test Results – CRD App
JDBC Driver | Avg. Heap Usage | Execution Time (ms)Dataset: 100 Million Records · 601 Columns
Metric Comparison: Average Heap Usage & Execution Time
mssql-jdbc (Before Optimization) | 311.34 MB | 5,017,218
mssql-jdbc (After Optimization) | 309.11 MB | 4,944,792
jTDS | 374.64 MB | 3,499,575