Cruisecontrolrb users - May 2008 - Cruisecontroi footprint for a virtual machine installation

Does anyone have any feel for the requirements (disk space, memory, anything
else you can think of) of a virtual machine (say Centos Linux), set up as a
CruiseControl.rb build machine?

Regards, Lori
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080525/60227d32/attachment.html>

Not much.  If you only run a single build, it is pretty much dependent
on the amount of memory you need for your build itself.  Disk space
can be controlled by proactively clearing out old build dirs/logs/etc.
 We''ve successfully run VMs of real rails app builds with only 256M of
RAM.  Of course, you want to keep an eye on that and ensure that
neither the virtual machine nor the host OS is swapping.

Bottom line, just try it out and keep a close eye on disk space and
memory on both the host OS and the virtual machine.

One caveat - Cruise.rb runs a separate builder process for each
project.  So, multiple projects - especially if you run them
concurrently - can really bog down the VM.  Even if you don''t run them
concurrently, you still need more memory for each additional project.

Hope this helps.

Good Luck,
-- Chad

On Sun, May 25, 2008 at 2:10 PM, Lori Olson <javadragon at gmail.com>
wrote:
> Does anyone have any feel for the requirements (disk space, memory,
anything
> else you can think of) of a virtual machine (say Centos Linux), set up as a
> CruiseControl.rb build machine?
>
> Regards, Lori
>
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
>

> Does anyone have any feel for the requirements (disk space, memory,
anything else you can think of) of a virtual machine (say Centos
Linux),
> set up as a CruiseControl.rb build machine?
On a couple of CC.rb installations I oversee, long living dashboard
processes tend to have RSS of about 40-50 Mb, and builder process are
around 35-40 Mb. MRI never releases memory back to the OS, so those are the
right numbers. Multiply by some safety factor and add whatever your build
process itself uses. 256 or 512 Mb should be it.

--Alex

Thanks, Alex.

On Wed, May 28, 2008 at 10:13 AM, Alexey Verkhovsky <
averkhov at thoughtworks.com> wrote:
> > Does anyone have any feel for the requirements (disk space, memory,
> anything else you can think of) of a virtual machine (say Centos Linux),
> > set up as a CruiseControl.rb build machine?
>
> On a couple of CC.rb installations I oversee, long living dashboard
> processes tend to have RSS of about 40-50 Mb, and builder process are
> around 35-40 Mb. MRI never releases memory back to the OS, so those are the
> right numbers. Multiply by some safety factor and add whatever your build
> process itself uses. 256 or 512 Mb should be it.
>
> --Alex
>
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080528/44b7f4a4/attachment.html>