feat: establish TCP connection to endpoint in advance#1
Draft
feat: establish TCP connection to endpoint in advance#1
Conversation
Use the EXECUTION_MARGIN_IN_SECONDS to resolve DNS and open a socket to reduce latency once the time is up
Member
Author
|
Marking as draft since I think the SQS timings could be tweaked to ensure we always have a little bit of leftover time to preconnect |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In order to speed up the delivery of our HTTP payloads we can take advantage of the fact that the SQS+Lambda integration will occassionally return messages a bit early. In the margin between SQS and actual
scheduledAtwe can resolve DNS and open a socket to reduce the amount of work that needs to happen once the job is meant to make its HTTP call.