TCP Callout Redesign in an RSS World

These are some notes about a discussion several of us (Adrian, Matt, Randall, Drew, Jonathan) had recently about TCP callouts, particularly in an RSS world.

These are my (Jonathan's) notes (and I've fleshed out the idea more than we discussed), so any errors are mine. (But, credit can go to the group.)



Create N threads per RSS bucket to handle TCP "session state maintenance" (which I am basically defining as the same things our timers do for us today).

If you really want to take this a step further, you could even do things like:

This is just a thumbnail sketch, but it should give the general idea. Hopefully, this will decrease cache misses, reduce lock contention, reduce the number of times we reschedule callouts, etc.

TransportProtocols/TCPCalloutRedesign (last edited 2016-10-06T17:01:47+0000 by JonathanLooney)