hazza/jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/jupyterhub.git synced 2025-10-17 06:52:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: Georgiana <georgiana.dolocan@gmail.com>
Co-authored-by: ajpower <122097973+ajpower@users.noreply.github.com>
This commit is contained in:
Min RK
2023-01-11 10:10:07 +01:00
committed by GitHub
parent c7402676a8
commit 52b8bc135f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/reference/database.md
View File

@@ -14,7 +14,7 @@ A lot of the operations in JupyterHub are also **relationships**, which is exact
For example:
- Given an API token, what user is making the request?
- Which users who don't have running servers?
- Which users don't have running servers?
- Which servers belong to user X?
- Which users have not been active in the last 24 hours?
@@ -52,7 +52,7 @@ Database operations are also synchronous, so while JupyterHub is waiting on a da
This allows us to avoid complex locking mechanisms, because transaction races can only occur during an `await`, so we only need to make sure we've completed any given transaction before the next `await` in a given request.
:::{note}
We are slowing working to remove these assumptions, and moving to a more traditional db session per-request pattern.
We are slowly working to remove these assumptions, and moving to a more traditional db session per-request pattern.
This will enable multiple Hub instances and enable scaling JupyterHub, but will significantly reduce the number of active users a single Hub instance can serve.
:::