Resource_usage.md - #302
Open
Graviton28 wants to merge 2 commits into
Open
Conversation
Graviton28
marked this pull request as ready for review
August 4, 2026 04:53
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
this whole doc was 100% dead clusters - xena, wheeler, gibbs, none of which exist anymore. rewrote with real current numbers for easley and hopper, pulled straight from sacctmgr (per-user QOS limits) and sinfo (partition walltimes/specs) on both clusters. also fixed the storage policy blurb - checked actual quota on easley, home dir is 100GB soft/200GB hard (not the old "200GB" flat number), and scratch has no personal quota enforced at all (confirmed with the quota command).
heads up: the soft/hard limit framing from the old PBS/Torque docs doesn't map cleanly onto how Slurm's QOS system actually works, so I presented these as "max per-user" limits per partition instead of forcing a soft/hard distinction that doesn't really exist anymore. if there's an official CARC policy doc elsewhere with different numbers, worth cross-checking against that, but everything here reflects what's actually configured on the clusters right now.