>> At the time when this was run there were 10 workers running, so this build
>> started out with 10 individual builds being executed in 10 workers (and VMs)
>> in
>> parallel. This build is one of them and it has taken ~ 2 hours to complete:
>
>> Each VM is assigned 1 CPU and 1.5 GB. They run:
>
>> travis@rails:~/travis-worker$ cat /proc/meminfo
>> MemTotal: 12323900 kB
>
> 10 * 1.5GB of RAM for the VMs makes ~15GB.
> As the host has only 12GB, I expect it to be busy swapping excessively
> (also the host will have some mem reserved...).
I saw this immediately after I've posted this, too :)
But actually it doesn't seem to swap. Is memory assigned to a VM dynamically,
as needed/used in the VM? Or is it assigned upfront?
Anyway I've reduced the memory per VM to 10GB and re-ran the tests, which
showed exactly the same behaviour.
> What if you only have e.g. 6 of the VMs running?
This has also been suggested when I asked on the #vbox channel on
irc.freenode.net last night.
I've re-run the tests with 5 VMs and got the following results.
The test that I was referring to in my initial post now took ~55 minutes. So
with N VMs/concurrent builds it took:
1 VM ~20 min http://staging.travis-ci.org/#!/svenfuchs/rails/builds/1927
5 VMs ~55 min http://staging.travis-ci.org/#!/svenfuchs/rails/builds/1985
10 VMs ~125 min
http://staging.travis-ci.org/#!/svenfuchs/rails/builds/1914
So it seems to degrade somewhat lineary with the number of VMs.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
