feat(rust): avoiding memory fragmentation by reducing allocations #8640
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 PR addresses the memory fragmentation from two sides, first many mini-allocations are avoided, mostly around
Route
, but also avoiding extra unused allocation in.ok_else(XXX)
.Then, to reduce the allocation of big chunks of memory, the
implementations/rust/ockam/ockam_core/src/buffer_pool.rs
was used to pool the buffers. To improve the benefits, the payload size was also increased to 96KB. This also means that the minimum bandwidth for a stable portal is 1Mbits.This combined helps reduce the fragmentation issue and stabilize the overall throughput by a lot.
BEFORE:
AFTER: