I think we could limit it by a certain number of days. However, just taking a look now, and it appears most projects have sane limits -- it could be the sheer number of projects that causes trouble. disk i/o on the master is pretty slow, anyway, it seems.
--j. On Fri, Feb 19, 2010 at 16:59, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > Hi, > > On Fri, Feb 19, 2010 at 5:37 PM, Justin Mason <j...@jmason.org> wrote: >> On Fri, Feb 19, 2010 at 14:42, Jukka Zitting <jukka.zitt...@gmail.com> wrote: >>> That's 30mins. Not sure what we can do to speed that up. >> >> Perhaps we should consider archiving old builds at this stage -- we >> have lots, alright. > > Agreed. I wouldn't be surprised if the large amount of old builds was > also a contributing factor to the OOM issue we saw earlier today. > > How about limiting build jobs to keeping just the ten latest builds by > default plus any builds that have explicitly been tagged? > > BR, > > Jukka Zitting > > -- --j.
