Il 06/10/20 16:53, Jason Simms ha scritto: > FWIW, I define the DefaultTime as 5 minutes, which effectively means for > any "real" job that users must actually define a time. It helps users > get into that habit, because in the absence of a DefaultTime, most will > not even bother to think critically and carefully about what time limit > is actually reasonable, which is important for, e.g., effective job > backfill and scheduling estimations. +1
> I currently don't have a MaxTime defined, because how do I know how long > a job will take? Most jobs on my cluster require no more than 3-4 days, > but in some cases at other campuses, I know that jobs can run for weeks. > I suppose even setting a time limit such as 4 weeks would be overkill, > but at least it's not infinite. I'm curious what others use as that > value, and how you arrived at it. We're currently using 24h,and will up to 72h. It's a compromise between users requesting more time for their jobs and how long they're willing to wait for their jobs to start. Checkpointing is always needed anyway. -- Diego Zuccato DIFA - Dip. di Fisica e Astronomia Servizi Informatici Alma Mater Studiorum - Università di Bologna V.le Berti-Pichat 6/2 - 40127 Bologna - Italy tel.: +39 051 20 95786
