{"id":587,"date":"2014-06-21T00:11:30","date_gmt":"2014-06-20T22:11:30","guid":{"rendered":"http:\/\/www.thelins.se\/johan\/blog\/?p=587"},"modified":"2014-06-21T22:53:42","modified_gmt":"2014-06-21T20:53:42","slug":"yocto-part-i-baseline-boot-time","status":"publish","type":"post","link":"https:\/\/www.thelins.se\/johan\/blog\/2014\/06\/yocto-part-i-baseline-boot-time\/","title":{"rendered":"Yocto part I – baseline boot time"},"content":{"rendered":"

The Yocto project<\/a> provides a set of tools to build custom distribution images from scratch. When using Yocto, the image, and all the tooling used to build the image, is built from recipes. These recipes are parsed using the bitbake<\/a> command. The recipes have dependencies, just as ordinary packages in a classical distro. By pointing to an image recipe, a dependency tree will be constructed and a large number of packages will be downloaded, built and then assembled into a single image.<\/p>\n

In this little series of blog posts, I aim to have a look at what can be done about size and performance for the minimal core image that comes with the system. The target system will be an x86 QEMU machine. So, my starting point is the outcome of the Yocto Project\u00a0Quick Start<\/a>. Before I get started, let me also point out the excellent Yocto Project Reference Manual<\/a>.<\/p>\n

My starting point is the core-image-minimal recipe, creating a minimal Linux system. It uses busybox, and provides very little, so it is a good baseline. I’d like to use systemd<\/a> for booting the image, so before building, I added the following lines to my local.conf file (info source<\/a>).<\/p>\n


\nDISTRO_FEATURES_append = \" systemd\"
\nVIRTUAL-RUNTIME_init_manager = \"systemd\"
\nDISTRO_FEATURES_BACKFILL_CONSIDERED = \"sysvinit\"
\nVIRTUAL-RUNTIME_initscripts = \"\"
\n<\/code><\/p>\n

I’m also keen on having a look at the boot performance, so I added systemd-analyze to the IMAGE_INSTALL variable. I did this by modifying the\u00a0meta\/recipes-core\/images\/core-image-minimal.bb file. I know that this is bad practice, I will explain how to do this properly using a custom meta layer and image recipe in a later installment of this series.<\/p>\n

Having built and started the system, I get a boot time of 11.3s. Of these, 6.4s are spent to start the kernel, while the remaining 4.9s are spent in userspace. I also got a nice boot graph, as well as a list of systemd units to blame for the time the boot sequence consumed. I used a little netcat trick<\/a> to get these files of the QEMU system to my host machine. Always nice, to avoid adding cruft to the image.<\/p>\n


\n1.272s systemd-udev-trigger.service
\n991ms systemd-user-sessions.service
\n694ms systemd-logind.service
\n363ms systemd-networkd.service
\n360ms systemd-remount-fs.service
\n353ms systemd-sysctl.service
\n299ms sys-kernel-debug.mount
\n292ms kmod-static-nodes.service
\n269ms dev-mqueue.mount
\n250ms systemd-tmpfiles-setup.service
\n242ms systemd-journal-flush.service
\n137ms systemd-update-utmp.service
\n129ms systemd-tmpfiles-setup-dev.service
\n102ms systemd-udevd.service
\n91ms tmp.mount
\n78ms systemd-random-seed.service
\n64ms var-volatile.mount
\n<\/code><\/p>\n

 <\/p>\n

\"Boot<\/a>
The boot chart.<\/figcaption><\/figure>\n

Next time, we will have a closer look on the base line image size, before we start looking at what we can do to optimize things.<\/p>\n","protected":false},"excerpt":{"rendered":"

The Yocto project provides a set of tools to build custom distribution images from scratch. When using Yocto, the image, and all the tooling used to build the image, is built from recipes. These recipes are parsed using the bitbake command. The recipes have dependencies, just as ordinary packages in a classical distro. By pointing … Continue reading Yocto part I – baseline boot time<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-587","post","type-post","status-publish","format-standard","hentry","category-yocto"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/posts\/587","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/comments?post=587"}],"version-history":[{"count":3,"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/posts\/587\/revisions"}],"predecessor-version":[{"id":601,"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/posts\/587\/revisions\/601"}],"wp:attachment":[{"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/media?parent=587"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/categories?post=587"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thelins.se\/johan\/blog\/wp-json\/wp\/v2\/tags?post=587"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}