Known causes of per-node performance degradations
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
- High load (more than number of CPUs on the node)
- High context switch frequency (lower-bound is somewhere above 100 kHz)
- High GPFS use
- Full
/tmpmount
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing documentation in the repository to find the appropriate place for node performance troubleshooting. Use the listed causes—load, context switches, GPFS use, and a full /tmp mount—as the required scope, preserving the stated thresholds. Done means these causes are documented clearly for operators, with no file or test path identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100