8000 feat: lower message loop sleep interval by ChaoticTempest · Pull Request #417 · sig-net/mpc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: lower message loop sleep interval #417

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

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

Conversation

ChaoticTempest
Copy link
Contributor

Testing this to see how much better our messaging is. In the future, sending messages out should be a bit smarter and more reactive by reaching the payload limit or timeout.

With this, I've noticed a slight performance increase in our test_signature_basic test by about 5-10s

volovyks
volovyks previously approved these changes Jun 23, 2025
@ChaoticTempest ChaoticTempest force-pushed the phuong/feat/lower-message-loop-interval branch from ea10309 to d7b12fc Compare June 25, 2025 13:08
@ChaoticTempest ChaoticTempest force-pushed the phuong/feat/lower-message-loop-interval branch from d7b12fc to 68e7374 Compare June 25, 2025 13:08
@@ -45,7 +45,7 @@ impl PositAction {
pub enum PositInternalAction<S> {
StartProtocol(Vec<Participant>, Positor<S>),
Reply(PositAction),
Rejected,
Abort,
Copy link
Contributor

Choose a reason for hiding this comment

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

why is this renamed in this PR? 😅

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because I promised to rename it in a different PR from this one: #421

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.

3 participants
0