Re: [slurm-users] Database Tuning w/SLURM

2019-03-22 Thread Ryan Novosielski
> On Mar 22, 2019, at 4:22 AM, Ole Holm Nielsen > wrote: > > On 3/21/19 6:56 PM, Ryan Novosielski wrote: >>> On Mar 21, 2019, at 12:21 PM, Loris Bennett >>> wrote: >>> >>> Our last cluster only hit around 2.5 million jobs after >>> around 6 years, so database conversion was never an issue.

Re: [slurm-users] Database Tuning w/SLURM

2019-03-22 Thread Ole Holm Nielsen
On 3/21/19 6:56 PM, Ryan Novosielski wrote: On Mar 21, 2019, at 12:21 PM, Loris Bennett wrote: Our last cluster only hit around 2.5 million jobs after around 6 years, so database conversion was never an issue. For sites with a higher-throughput things may be different, but I would hope that

Re: [slurm-users] Database Tuning w/SLURM

2019-03-21 Thread Prentice Bisbal
On 3/21/19 1:56 PM, Ryan Novosielski wrote: On Mar 21, 2019, at 12:21 PM, Loris Bennett wrote: Our last cluster only hit around 2.5 million jobs after around 6 years, so database conversion was never an issue. For sites with a higher-throughput things may be different, but I would hope tha

[slurm-users] Database Tuning w/SLURM (was: Re: SLURM heterogeneous jobs, a little help needed plz)

2019-03-21 Thread Ryan Novosielski
> On Mar 21, 2019, at 12:21 PM, Loris Bennett > wrote: > > Our last cluster only hit around 2.5 million jobs after > around 6 years, so database conversion was never an issue. For sites > with a higher-throughput things may be different, but I would hope that > at those places, the managers wo