8000 perf: don't clone all incoming `PeerMessage`s by jakmeier · Pull Request #9559 · near/nearcore · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

perf: don't clone all incoming PeerMessages #9559

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

Merged
merged 1 commit into from
Sep 22, 2023

Conversation

jakmeier
Copy link
Contributor

The clone was only there because of lifetime complaints that were due to the message being moved to the test observer after processing. We can avoid the clone entirely in non-test setup.

This is important because these messages can be 100MB+

The clone was only there because of lifetime complaints that were due
to the message being moved to the test observer after processing.
We can avoid the clone entirely in non-test setup.

This is important because these messages can be 100MB+
@jakmeier jakmeier requested a review from saketh-are September 21, 2023 19:04
@jakmeier jakmeier requested a review from a team as a code owner September 21, 2023 19:04
@jakmeier jakmeier enabled auto-merge September 21, 2023 19:04
@jakmeier jakmeier changed the title perf: don't clone all incoming PeerMessage perf: don't clone all incoming PeerMessages Sep 21, 2023
@jakmeier jakmeier added this pull request to the merge queue Sep 22, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 22, 2023
@jakmeier jakmeier added this pull request to the merge queue Sep 22, 2023
Merged via the queue into near:master with commit e5c6d1e Sep 22, 2023
@jakmeier jakmeier deleted the avoid_peer_message_clone branch September 22, 2023 16:22
nikurt pushed a commit that referenced this pull request Sep 26, 2023
The clone was only there because of lifetime complaints that were due to
the message being moved to the test observer after processing. We can
avoid the clone entirely in non-test setup.

This is important because these messages can be 100MB+
nikurt pushed a commit that referenced this pull request Sep 26, 2023
The clone was only there because of lifetime complaints that were due to
the message being moved to the test observer after processing. We can
avoid the clone entirely in non-test setup.

This is important because these messages can be 100MB+
nikurt pushed a commit that referenced this pull request Oct 11, 2023
The clone was only there because of lifetime complaints that were due to
the message being moved to the test observer after processing. We can
avoid the clone entirely in non-test setup.

This is important because these messages can be 100MB+
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0