Skip to content
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

remove faulty de-duplication condition for seen aggregates #2225

Merged
merged 1 commit into from Mar 15, 2021

Conversation

djrtwo
Copy link
Contributor

@djrtwo djrtwo commented Mar 11, 2021

Addresses #2183

The alternative would be to have a more exotic message-id that is only a function of aggregate_and_proof.aggregate.

I suggest we observe mainnet's aggregation data and make a call.

Copy link
Collaborator

@protolambda protolambda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. May cost some bandwidth, but is more robust, and works with what we have.

@djrtwo djrtwo merged commit 6f473af into dev Mar 15, 2021
@djrtwo djrtwo deleted the seen-aggregates branch March 15, 2021 13:43
arnetheduck added a commit to status-im/nimbus-eth2 that referenced this pull request Feb 25, 2022
ethereum/consensus-specs#2225 removed an ignore
rule that would filter out duplicate aggregates from gossip publishing -
however, this causes increased bandwidth and CPU usage as discussed in
ethereum/consensus-specs#2183 - the intent is
to revert the removal and reinstate the rule.

This PR implements ignore filtering which cuts down on CPU usage (fewer
aggregates to validate) and bandwidth usage (less fanout of duplicates)
- as #2225 points out, this may lead to a small increase in IHAVE
messages.
arnetheduck added a commit to status-im/nimbus-eth2 that referenced this pull request Feb 25, 2022
ethereum/consensus-specs#2225 removed an ignore
rule that would filter out duplicate aggregates from gossip publishing -
however, this causes increased bandwidth and CPU usage as discussed in
ethereum/consensus-specs#2183 - the intent is
to revert the removal and reinstate the rule.

This PR implements ignore filtering which cuts down on CPU usage (fewer
aggregates to validate) and bandwidth usage (less fanout of duplicates)
- as #2225 points out, this may lead to a small increase in IHAVE
messages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants