docs: clarify troubleshooting performance with Django authentication #570
Conversation
This file contains 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
Using the builtin Django authentication system on the API server results in very significant performance degradation. The documentation already strongy suggests delegating authentication to a load balancer / reverse proxy but some people might still rely on the default authentication while experimenting. The Troubleshooting section hinted that the performance issue could be due to Django<->database latency, when it is in fact due to the use of PBKDF2 for password hashing.
|
Build succeeded. ✔️ ara-tox-py3 SUCCESS in 3m 02s |
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.
Summary
This PR is related to #283. Feel free (of course) to close if you think it's not necessary!
Using the builtin Django authentication system on the API server results in very significant performance degradation. The documentation already strongy suggests delegating authentication to a load balancer / reverse proxy but some people might still rely on the default authentication while experimenting.
The Troubleshooting section hinted that the performance issue could be due to Django<->database latency, when it is in fact due to the use of PBKDF2 for password hashing.