BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Denver
X-LIC-LOCATION:America/Denver
BEGIN:DAYLIGHT
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
TZNAME:MDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
TZNAME:MST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20200129T163557Z
LOCATION:405-406-407
DTSTART;TZID=America/Denver:20191122T103000
DTEND;TZID=America/Denver:20191122T103700
UID:submissions.supercomputing.org_SC19_sess129_ws_hpcsysp104@linklings.co
 m
SUMMARY:Arbiter: Dynamically Limiting Resource Consumption on Login Nodes
DESCRIPTION:Workshop\n\nArbiter: Dynamically Limiting Resource Consumption
  on Login Nodes\n\nGardner, Migacz, Haymore\n\nLogin nodes are shared reso
 urces that are meant for small, lightweight tasks such as submitting to th
 e batch system, scripting, compiling, and staging data. Because they are s
 hared resources, the responsiveness of login nodes depends on users being 
 good citizens with respect to CPU time and memory usage. Many HPC centers 
 have policies that define behavior that is acceptable. However, the unfort
 unate reality is that users frequently violate these policies and negative
 ly impact the work of others. This impact is exacerbated by the fact that 
 administrators often have to police users’ behavior.<br /><br />Arbi
 ter is a service that addresses the misuse of login nodes by automatically
  enforcing policies using cgroups. When users log in, Arbiter sets a defau
 lt hard memory and CPU limit on the user to prevent them from dominating t
 he whole machine’s memory and CPU resources. To enforce policies, Ar
 biter tracks the usage of individual users over a set interval and looks f
 or policy violations. When a violation occurs, the violating user is email
 ed about what behavior constituted the violation and the acceptable usage 
 policy for login nodes. In addition, Arbiter also temporarily lowers the h
 ard memory and CPU limit to discourage excessive usage. The length of time
  and severity of the lower hard limit depends on whether a user has repeat
 edly violated policies to penalize users for continued excessive usage. Th
 e result of the Arbiter service is that login nodes stay responsive, with 
 users informed of policies and discouraged from running computationally he
 avy jobs on login nodes.\n\nTag: Workshop Reg Pass, Datacenter, SIGHPC Wor
 kshop, State of the Practice, System Administration, System Maintenance, S
 ystem Reliability\n\nRegistration Category: Workshop Reg Pass, Datacenter,
  SIGHPC Workshop, State of the Practice, System Administration, System Mai
 ntenance, System Reliability
URL:https://sc19.supercomputing.org/presentation/?id=ws_hpcsysp104&sess=se
 ss129
END:VEVENT
END:VCALENDAR