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.

Sign up for GitHub

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

Jump to bottom

JARM tls algorithm should use connection pooling #576

Closed
Mzack9999 opened this issue Apr 11, 2022 · 0 comments · Fixed by #707 or #715
Closed

JARM tls algorithm should use connection pooling #576

Mzack9999 opened this issue Apr 11, 2022 · 0 comments · Fixed by #707 or #715
Assignees
@Ice3man543
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity.

Comments

@Mzack9999
Copy link
Member

httpx version:

v1.2.1-dev

Current Behavior:

JARM algorithm performs 10 sequential TCP connections with standard backoff and large timeout

Expected Behavior:

The probes should be parallelized or make use of speculative connection pool (pre-creating idle connections)

Steps To Reproduce:

None
@Mzack9999 Mzack9999 added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Apr 11, 2022
@Mzack9999 Mzack9999 added the Status: On Hold Similar to blocked, but is assigned to someone label Apr 20, 2022
@Mzack9999 Mzack9999 changed the title Recently added JARM tls algorithm should use connection pooling JARM tls algorithm should use connection pooling Apr 20, 2022
@ehsandeep ehsandeep mentioned this issue Jun 16, 2022
Closed
@ehsandeep ehsandeep added Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity. and removed Status: On Hold Similar to blocked, but is assigned to someone labels Jul 10, 2022
@Ice3man543 Ice3man543 self-assigned this Jul 24, 2022
@Ice3man543 Ice3man543 mentioned this issue Jul 24, 2022
Merged
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Jul 25, 2022
@ehsandeep ehsandeep linked a pull request Jul 31, 2022 that will close this issue
Bugfix release #715
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Ice3man543 Ice3man543

Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity.
Projects
None yet
Milestone
No milestone
3 participants
@ehsandeep @Mzack9999 @Ice3man543