Hi Chris, On Sun, Sep 25, 2016 at 04:51:32PM -0700, Christopher Samuel wrote:
> > On 23/09/16 19:12, Miguel Gila wrote: > > > We also do this, run a number of Slurm clusters attached to a single > > slurmdbd. One issue with this is setup is that once you decommission > > a cluster, it needs to be removed from the DB somehow, otherwise your > > DB grows beyond reasonable size... > > For accounting reasons we can't do that, consequently our slurmdbd is > around 17GB in size. > > To give you an idea the largest table is the job step table for our > BlueGene/Q which takes almost 7GB for pushing 19 million job steps. > > The next largest is the job step table for one of our x86 clusters which > is around 3GB for 8 million job steps. Just curious, is there a reason you don't Purge the step (or job) data? E.g. PurgeStepAfter=1month PurgeJobAfter=12month Do you need to run detailed historical job reports, or push the data to another system (you mentioned XDMoD in a different thread)? Paddy -- Paddy Doyle Trinity Centre for High Performance Computing, Lloyd Building, Trinity College Dublin, Dublin 2, Ireland. Phone: +353-1-896-3725 http://www.tchpc.tcd.ie/
