----- Original Message ----- | From: "David Kutalek" <[email protected]> | To: [email protected] | 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 [email protected] https://www.redhat.com/mailman/listinfo/devtools
