mirror of
https://github.com/jupyterhub/the-littlest-jupyterhub.git
synced 2025-12-18 21:54:05 +08:00
small updates to the docs
This commit is contained in:
@@ -40,9 +40,16 @@ Maximum memory allowed per user
|
||||
|
||||
Depending on what kinda work your users are doing, they will use different amounts
|
||||
of memory. The easiest way to determine this is to run through a typical user
|
||||
workflow yourself, and measure how much memory is used. Add 20-40% headroom for
|
||||
users to 'play around', and that should be the maximum memory allowed per user.
|
||||
The system will prevent users from using more memory than this.
|
||||
workflow yourself, and measure how much memory is used.
|
||||
|
||||
For example, you can begin running a Jupyter Notebook session on your JupyterHub, then open a
|
||||
terminal on the JupyterHub and use ``top`` to track how much memory you use
|
||||
as you go through the material. A good rule of thumb is to take the maximum amount of memory you used during
|
||||
your session, and add 20-40% headroom for users to 'play around'. This is the
|
||||
maximum amount of memory that should be given to each user.
|
||||
|
||||
If users use *more* than this alloted amount of memory, their kernel will restart (and all
|
||||
their progress in the current session will be lost).
|
||||
|
||||
CPU
|
||||
===
|
||||
@@ -56,7 +63,7 @@ stop, unlike with RAM.
|
||||
Server CPU Recommended = (Maximum concurrent users \times Maximum CPU usage per user) + 0.2
|
||||
|
||||
The ``0.2`` is overhead for TLJH and related services. **Server CPU Recommended**
|
||||
is the amount of CPU the server you aquire should have. We recommend using
|
||||
is the amount of CPU the server you acquire should have. We recommend using
|
||||
the same process used to estimate Memory required for estimating CPU required.
|
||||
|
||||
Disk space
|
||||
|
||||
Reference in New Issue
Block a user