14. Yen Policy
|Platform||CPU Limit||Memory Limit|
|Interactive Yens (
||12||320 GB (21%)|
|JupyterHub||12||320 GB (21%)|
||62||48 GB per CPU|
This page outlines usage guidelines for the yens with respect to system resources. See our Topic Guides page for specific resource management techniques for commonly used software on the yens, including Python, Matlab, R and Stata/MP.
The yen systems comprise a shared cluster that hosts many researchers at the GSB. As these are powerful systems (currently 32 CPUs and 1.5 TB RAM per yen), it is common for them to be used for complex jobs that may take hours, days or even longer to complete. For this reason it is important that all users of these systems understand how to limit their momentary resource footprints so that the larger community is not negatively impacted.
When using the yens, please adhere to some community best practices:
- Be aware of your resource footprint
- Restrict your code to a maximum of 12 cores and 320 GB of RAM
- Clean up temporary files to free up disk space
gsbquotato ensure you don’t exceed your quota
- Check in on large jobs periodically
- Avail yourself of platform-specific techniques that limit resource gobbling
- When in doubt, ask!
Take the time to understand how your code will impact the environment in which it runs. Is your platform configured to claim all available resources (please fix that)? Are you actively using all of the RAM you have (consider saving to disk or clearing that out)? Is one of the yens particularly impacted during conference season (try another yen)? You are part of a community, and overuse impacts everyone. Please be a good neighbor!
Monitor Your Children
htop are typical, easy to understand tools that can provide quick insights into all the system’s processes, including your own. Columns in both tools can be sorted by CPU, RAM, VRAM, or PID.
htop also provides nice CPU graphs. Make sure your job is behaving as expected - pay particular attention to processes that use increasing amounts of RAM or try to use all available CPUs. If you notice a problem, halt your job and fix the issue before restarting it.
If you are claiming too much CPU or RAM at one time then your jobs will be automatically killed, or the DARC team may contact you directly to ask you to terminate your job. This is always a drag for everybody. Please don’t make us do this.