Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

Profile socket flush behavior #35

Open
willscott opened this issue Jul 28, 2022 · 1 comment
Open

Profile socket flush behavior #35

willscott opened this issue Jul 28, 2022 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@willscott
Copy link
Contributor

the generated server is agressive in flushing the write stream, e.g. here.

This may result in tcp packets being sent with just header information, since flush is called, and result in double the http framing overhead.

Do we need the immediate flush of headers in the case that a result can be provided on the channel in a synchronous fashion? is there a way to only flush headers after a few milliseconds if an immediate result is not forthcoming from the handler?

@willscott willscott added the need/triage Needs initial labeling and prioritization label Jul 28, 2022
@welcome
Copy link

welcome bot commented Jul 28, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant