fuel-dev team mailing list archive

[Andrey Korolev <akorolev@xxxxxxxxxxxx>]

I`d like to suggest in-memory compression, way better than swap and
will increase effective rss snapshot size almost twice, especially on
smaller VMs (with ratio 0.6...0.7):

http://repo.flops.ru/debian/pool/free/z/zram-swap/ , versions for all
other distros can be fetched there too.

On Thu, Aug 21, 2014 at 1:47 PM, Mike Scherbakov
<mscherbakov@xxxxxxxxxxxx> wrote:
> I would disable swap at all. If we run out of memory, we simply fail the
> build, instead of overusing disk.
> If it's really that much of memory needed (I'd like to know details though
> what services need that much), then looks like we have no other choice than
> to increase memory for envs.
>
> Thanks,
> Mike Scherbakov
> #mihgen
>
> On Aug 21, 2014 1:41 PM, "Sergii Golovatiuk" <sgolovatiuk@xxxxxxxxxxxx>
> wrote:
>>
>> Hi,
>>
>> Digging the issue with Galera, I found that our environments have very
>> high RAM utilization which leads to the problem during environment
>> deployment. For instance "HA deployment + neutron/GRE" requires almost
>> 2.6-2.7 GB during deployment
>> (corosync+mysql+puppet++rabbit+neutron+ovs+openstack services). I found high
>> swap in/swap out usage during deployment with very high load average. This
>> creates many sporadic issues with some services. They time out in random
>> place making our debugging very hard. I would like to review our policy for
>> CI environment and increase RAM (at least for bvt tests) to 3 GB.
>>
>> --
>> Best regards,
>> Sergii Golovatiuk,
>> Skype #golserge
>> IRC #holser
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>