You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on near/mpc#412 I noticed that there are about 3 times as many messages getting sent as I'd expect when running this test. When running 10 nodes there are this many messages in sent to each node.
48
165
292
419
546
673
800
927
1054
1191
About 3% of the messages being sent are duplicates, I'd like to make sure that each message is being acted upon.
Also 9 messages are sent to completed triples even when the threshold is n/n, I'd like that behaviour to be explained and documented somewhere.
The text was updated successfully, but these errors were encountered:
Probably the duplicate messages you were seeing is the send many, where node A relays the same message to node B and node C. I had a duplicate filter for a mapping of (sender_id, receiver_id, message) -> count and saw only unique counts. Additionally, tried doing a filter on duplicate messages being sent to a receiver but that actually fails to complete the triple generation. So a node receiving the same message but from different senders is still valid
While working on near/mpc#412 I noticed that there are about 3 times as many messages getting sent as I'd expect when running this test. When running 10 nodes there are this many messages in sent to each node.
About 3% of the messages being sent are duplicates, I'd like to make sure that each message is being acted upon.
Also 9 messages are sent to completed triples even when the threshold is n/n, I'd like that behaviour to be explained and documented somewhere.
The text was updated successfully, but these errors were encountered: