Skip to content
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

ref(server): Manually control concurrent upstream requests #678

Merged
merged 20 commits into from
Aug 18, 2020

Conversation

RaduW
Copy link
Contributor

@RaduW RaduW commented Jul 24, 2020

WIP Move implementation from all upstream requests being sent when they are created
to sending them only when there are free http connections available.

Still to do:
- consuming loop not done
- figure out if we can do consuming loop somehow in the actor thread or
we need to spanw thread ( and change request sender not to receive self)
@RaduW RaduW requested a review from a team July 24, 2020 16:10
@RaduW RaduW changed the title ref(server): Manualy control concurent upstream requests. ref(server): WIP Manually control concurrent upstream requests. Jul 24, 2020
@RaduW RaduW marked this pull request as draft July 24, 2020 16:15
- still missing free http connection counters
@RaduW RaduW marked this pull request as ready for review August 14, 2020 09:19
@RaduW RaduW changed the title ref(server): WIP Manually control concurrent upstream requests. ref(server): Manually control concurrent upstream requests. Aug 14, 2020
Copy link
Member

@jan-auer jan-auer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, the approach looks great. Below are nit picks and naming changes.

relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/actors/upstream.rs Outdated Show resolved Hide resolved
relay-server/src/utils/tracked_future.rs Outdated Show resolved Hide resolved
relay-server/src/utils/tracked_future.rs Outdated Show resolved Hide resolved
Instead of using an mpsc channel to notify the end of a tracked future
now we use an `Recipient<TrackedFutureFinished>` with the handler
implemented in `UpstreamRelay`
@RaduW RaduW requested a review from jan-auer August 17, 2020 16:04
@jan-auer jan-auer changed the title ref(server): Manually control concurrent upstream requests. ref(server): Manually control concurrent upstream requests Aug 18, 2020
@RaduW RaduW merged commit c9556fb into master Aug 18, 2020
@RaduW RaduW deleted the ref/priority-upstream branch August 18, 2020 10:39
jan-auer added a commit that referenced this pull request Aug 18, 2020
* master:
  fix: Coerce missing PR body to empty string
  meta(gh): Add a status check for changelogs (#700)
  ref(server): Manually control concurrent upstream requests (#678)
  fix(docs): Clarify sooner which mode to choose (#709)
  chore(config): Remove config for emitting attachment flags (#718)
  fix(protocol): Fix docs typo (#719)
  fix(doc): Add missing newlines (#717)
  ci(release): Add killswitch via issues w/ release-blocker label (#714)
  fix: Add changelog entry for #712 (#716)
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.

2 participants