-
Notifications
You must be signed in to change notification settings - Fork 52
Batch messages between Web Workers so there's only one ever in flight #269
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
Conversation
|
What is the 'not for commot' reservation? I'll provide comments regardless,
|
|
I just didn't want anyone to click "merge", or feel time pressure to
|
|
Just cleaning house, is this pull request still relevant? Thanks! |
|
I still think there might be a chance to gain ~5-10% on uProxy throughput with a technique like this. Now that we have better benchmarking tools it might be time to revisit this. |
|
Sounds good, let me know if you'd like me to take a look. |
|
Another cleaning-house revisit - if this is still relevant I'm happy to take a look. Thanks! |
|
Yeah, we don't need to hold this open. I'll reopen if we have evidence that it's worthwhile. |
NOT FOR COMMIT
This change is designed to reduce the number of messages sent in very high load situations.
It appears to improve throughput in uproxy-churn by about 10%.