[Devtools] CDK performance ideas

Burr Sutter bsutter at redhat.com
Tue Apr 19 08:57:10 UTC 2016


We gave birth to Helloworld MSA at last nights NYC Java Meetup
https://github.com/redhat-helloworld-msa

I have noticed that when running our demo in the CDK (with 6GB of RAM) it
slow eats away at memory.  I tend to leave the VM up and sleep my computer,
upon awake, it tends to have lost some memory.   Also, if you are
performing builds in Openshift, it loses memory much faster - theory is
that the build pods are not garbage collected.

If you run with only 4GB of RAM, you can get into a state that swapping
starts up and kswapd0 will consume 100% of CPUs and essentially "lock up"
the CDK's VM.

So, we need some strategies for people to "clean up" their RAM and their
disk space, without "vagrant destroy"  :-)



On Tue, Apr 19, 2016 at 4:22 AM, Praveen Kumar <prkumar at redhat.com> wrote:

>
>
> ----- Original Message -----
> | From: "David Kutalek" <dkutalek at redhat.com>
> | To: devtools at redhat.com
> | Sent: Tuesday, April 19, 2016 1:44:45 PM
> | Subject: [Devtools] CDK performance ideas
> |
> | Hi folks,
> |
> | there are some ideas for future sppedup of cdk box I had in queue,
> | want to give them out now in expectation that someone on developer side
> | can engage more.
> |
> | 1) Grub delay
> |
> |    Grub has 5 seconds timeout in CDK. We can probably change to 1 or
> even 0.
> |
> | 2) Initrd delay
> |
> |    Roughly 4 seconds, probably not worth the optimization in first round.
> |
> | 2) Starting services
> |
> |    Probably starting bunch of services which are not needed.
> |    By far longest one is kdump.
> |
> |    - quickly tried systemd-analyze on CDK after first boot:
> |      - biggest thing - kdump took ~ 25seconds and system is waiting for
> it
> |        do we need it in cdk box by default?
> |      - probably bunch of small things for no reason, like
> |        wpa supplicant service - no wifi in cdk
> |    - we could investigate possibilities of
> |      systemd-readahead-collect and systemd-readahead-replay
> |      (although probably not so useful in vm)
> |
> | Hope this helps,
>
> Great findings, We can create issues (on Github[0]) for each point and
> work/discuss those, easy way to track.
>
> [0] https://github.com/projectatomic/adb-atomic-developer-bundle
>
> --
> Praveen Kumar
> https://fedoraproject.org/wiki/User:Kumarpraveen
>
> _______________________________________________
> Devtools mailing list
> Devtools at redhat.com
> https://www.redhat.com/mailman/listinfo/devtools
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20160419/83906917/attachment.htm>


More information about the Devtools mailing list