Skip to content

Conversation

@bemasc
Copy link
Contributor

@bemasc bemasc commented May 13, 2015

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%.

@willscott
Copy link
Member

What is the 'not for commot' reservation? I'll provide comments regardless,
probably tomorrow.
On May 13, 2015 5:46 PM, "Benjamin M. Schwartz" notifications@github.com
wrote:

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%.

You can view, comment on, or merge this pull request online at:

#269
Commit Summary

  • Batch messages between Web Workers so there's only one ever in flight
  • Try a more extreme batching.
  • Cover a possible corner case, and add YUIDoc
  • Fix logic bug: forgot to reset pendingAcks!
  • Fix variable name error
  • Raise the limit to 10 messages.
  • A queue limit of 2 seems to be slightly faster than 10.

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#269.

@bemasc
Copy link
Contributor Author

bemasc commented May 14, 2015

I just didn't want anyone to click "merge", or feel time pressure to
review, because the gain isn't as big as I thought, and it depends on the
limit in maybeSend in a way that I don't really understand.
On May 13, 2015 6:55 PM, "Will" notifications@github.com wrote:

What is the 'not for commot' reservation? I'll provide comments regardless,
probably tomorrow.
On May 13, 2015 5:46 PM, "Benjamin M. Schwartz" notifications@github.com
wrote:

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%.

You can view, comment on, or merge this pull request online at:

#269
Commit Summary

  • Batch messages between Web Workers so there's only one ever in flight
  • Try a more extreme batching.
  • Cover a possible corner case, and add YUIDoc
  • Fix logic bug: forgot to reset pendingAcks!
  • Fix variable name error
  • Raise the limit to 10 messages.
  • A queue limit of 2 seems to be slightly faster than 10.

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#269.


Reply to this email directly or view it on GitHub
#269 (comment).

@agallant
Copy link

Just cleaning house, is this pull request still relevant? Thanks!

@bemasc
Copy link
Contributor Author

bemasc commented Oct 21, 2015

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.

@agallant
Copy link

Sounds good, let me know if you'd like me to take a look.

@agallant
Copy link

Another cleaning-house revisit - if this is still relevant I'm happy to take a look. Thanks!

@bemasc
Copy link
Contributor Author

bemasc commented May 23, 2016

Yeah, we don't need to hold this open. I'll reopen if we have evidence that it's worthwhile.

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.

4 participants