-
-
Notifications
You must be signed in to change notification settings - Fork 563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(rust): avoiding memory fragmentation by reducing allocations #8640
Merged
Conversation
This file contains 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
davide-baldo
force-pushed
the
davide-baldo/avoid-memory-fragmentation
branch
9 times, most recently
from
November 14, 2024 17:40
bee4614
to
d432379
Compare
davide-baldo
force-pushed
the
davide-baldo/avoid-memory-fragmentation
branch
2 times, most recently
from
November 26, 2024 16:53
d93bed7
to
c73ab96
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice improvements!
implementations/rust/ockam/ockam_vault/src/software/vault_for_signing/vault_for_signing.rs
Show resolved
Hide resolved
implementations/rust/ockam/ockam_core/src/routing/message/local_message.rs
Show resolved
Hide resolved
implementations/rust/ockam/ockam_core/src/routing/message/local_message.rs
Show resolved
Hide resolved
implementations/rust/ockam/ockam_transport_tcp/src/portal/portal_message.rs
Outdated
Show resolved
Hide resolved
implementations/rust/ockam/ockam_identity/src/secure_channel/key_tracker.rs
Outdated
Show resolved
Hide resolved
implementations/rust/ockam/ockam_identity/src/secure_channel/key_tracker.rs
Outdated
Show resolved
Hide resolved
davide-baldo
force-pushed
the
davide-baldo/avoid-memory-fragmentation
branch
from
November 26, 2024 19:26
c73ab96
to
0b9d541
Compare
davide-baldo
force-pushed
the
davide-baldo/avoid-memory-fragmentation
branch
from
November 27, 2024 10:02
0b9d541
to
5b04957
Compare
davide-baldo
force-pushed
the
davide-baldo/avoid-memory-fragmentation
branch
from
November 28, 2024 12:08
5b04957
to
ebefe6e
Compare
SanjoDeundiak
approved these changes
Dec 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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)
.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.
BEFORE:
AFTER: