Https benchmark #5
Open
Conversation
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
The new benchmark starts a TLS secured server and spawns clients to connect, validate the certificate chain, and GET the root resource. The certificate chains are generated using the cryptography package.
The goal of the benchmark is to assess the performance of an HTTPS get, with hostname and certificate validation. Hostname lookup will add overhead to the benchmark that, while real in production, is also variable depending on the environment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a benchmark to test, as much as possible, the HTTPS features of twisted. This benchmark intentionally tries to bypass all hostname lookup overhead (though I may not have plugged a resolver correctly) and focus only on certificate validation and hostname verification.
Thanks in advance for reviews.