PoC: Faster HANA streaming #1426
Draft
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 explorers a possible way to avoid certain network protocol deficiencies. To unlock greater single connection and overall throughput capabilities for the
@cap-js/hanaservice.The current performance measurements can be found here.
For the measurements of this PR
node@24was used as this comes with optimizations that also improve throughput.hanamainhanafasterpostgresmainIn the case of
postgresthe same approach observed a large reduction in performance (~50%), caused by materialization insidepostgrescausing memory troubles. By just upgrading tonode@24thepostgresthroughput went up by~50%. For HANA once the network package management is avoided the single connection performance becomes more stable. The major impact is on the throughput as the network capacity is utilized to its fullest extend. Enabling the capability to download 1million books in a single second. With a peak application memory of~50mbduring the whole process.