Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Experiment to try to use forgetful blooms to dedup gossip #280

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Vagabond
Copy link
Contributor

No description provided.

Copy link
Contributor

@andymck andymck left a comment

Choose a reason for hiding this comment

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

It looks like you are applying the filters on received data and avoiding having to handle it and thus if we have already handled it we avoid gossiping to our peers a subsequent time.
But our peer list will change, so I would not have thought it ideal to assume because my peer has previously seen it, we dont need to gossip it to any of our current peers.

I had thought, originally, your intent was to apply the filter to outgoing data on a per peer basis. In that model you would always attempt to gossip data that you receive but will avoid sending it to peers you previously gossiped that same data too. This could be achieved by using the filter on at the group_worker:send level.....

{_, Pids} = lists:unzip(connections(all, State)),
%% track we've seen this now
forgetful_bloom:set(Bloom, {Key, Data}),
Copy link
Contributor

Choose a reason for hiding this comment

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

At this point ( in the gossip server ) we do not know whether the send will be successful. For example a stream may not yet be associated with the worker

@evanmcc evanmcc marked this pull request as ready for review July 19, 2021 22:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants