Running mash in Koji

Mathieu Bridon bochecha at fedoraproject.org
Wed Oct 2 03:53:35 UTC 2013


Hi, and thanks for the feedback Kevin,

On Thu, 2013-09-26 at 10:32 -0600, Kevin Fenzi wrote:
> On Tue, 24 Sep 2013 12:38:44 +0800
> Mathieu Bridon <bochecha at fedoraproject.org> wrote:
> > 1. What would be an appropriate weight for this new task?
> > 
> > At the moment I'm just using the default, but given that mashing can
> > be quite intensive, it might be better to increase that. I have no
> > idea on what would be the right number, though.
> 
> Yeah, not sure either... but I wonder if it wouldn't make sense to make
> this it's own channel so it could go to specific builders. 
> 
> In the Fedora case we would want that as our mashes are very memory
> intensive (mostly due to deltarpm generation), so if somehow an arm
> builder got it, not sure how long it would take it to finish (if ever). 

Good point, I'll work on that.

> > 3. What to do with the output?
[... snip ...]
> 
> Not sure. For some data to toss in tho, a current rawhide mash takes
> up about 163GB. Branched f20 is currently around 153GB. 
> 
> So, in addition to the question of if it should try and upload to the
> hub or not, it needs to make sure and have enough local working space
> to hold all that (unless it's writing to a rw /mnt/koji for that). 

So first of all, do the Fedora builders have that kind of space
available?

Mike, given the above, do you still think uploading is the best path
forward?

Thanks,


-- 
Mathieu



More information about the buildsys mailing list