Ticket 3653

Summary:	Revisit 'scontrol top' implementation
Product:	Slurm	Reporter:	Tim Wickberg <tim>
Component:	User Commands	Assignee:	Dominik Bartkiewicz <bart>
Status:	RESOLVED FIXED	QA Contact:
Severity:	5 - Enhancement
Priority:	---
Version:	17.11.x
Hardware:	Linux
OS:	Linux
Site:	SchedMD	Slinky Site:	---
Alineos Sites:	---	Atos/Eviden Sites:	---
Confidential Site:	---	Coreweave sites:	---
Cray Sites:	---	DS9 clusters:	---
Google sites:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	NoveTech Sites:	---
Nvidia HWinf-CS Sites:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Tzag Elita Sites:	---
Linux Distro:	---	Machine Name:
CLE Version:		Version Fixed:	17.11.1
Target Release:	18.08	DevPrio:	4 - Medium
Emory-Cloud Sites:	---

Description Tim Wickberg 2017-03-31 13:22:24 MDT

The current implementation of 'scontrol top' has a number of weaknesses.

With the current implementation of manipulating the 'nice' priority of other jobs, repeated usage will continue to push priorities of all jobs by that user further downwards. It also falls short in the face of new job submissions by that user, which may come in at a lower priority.