[libvirt PATCH] ci: maximize cirrus CI ram/cpu allocation

[Daniel P. Berrangé]

On Wed, Jul 21, 2021 at 01:07:04PM +0200, Michal Prívozník wrote:
> On 7/20/21 5:05 PM, Daniel P. Berrangé wrote:
> > For macOS you always get the maximum configuration by default (12 CPUs,
> > 24 GB RAM), but for FreeBSD you get 2 CPUs, 4 GBs by default. This
> > change increases the allocation to 8 CPUs, 8 GBs for FreeBSD.
> > 
> > Signed-off-by: Daniel P. Berrangé <berrange at redhat.com>
> > ---
> > 
> > In theory this could make builds quicker. In practice I've not been
> > able to measure a difference due to large variance between runs.
> > 
> >  .gitlab-ci.yml      | 8 ++++++++
> >  ci/cirrus/build.yml | 2 ++
> >  2 files changed, 10 insertions(+)
> 
> A slightly offtopic question - is there a limit how many builds can we
> run in given time frame, or how much resources can we consume? If so,
> how far are we from getting rate limited? My understanding is that we
> are using a free plan and I bet there would be some sort of limit.

Cirrus doesn't limit overall consumption of resources, but it does
limit job parallelism. IIRC, you can only have 2 jobs runing at any
point in time in Cirrus. So we need to keep the number of jobs low.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|