Skip to content

Latest commit

 

History

History
60 lines (44 loc) · 2.86 KB

benchmark.md

File metadata and controls

60 lines (44 loc) · 2.86 KB
Raw

Benchmark

This document is meant to provide some statistics about the performance of the project, in order for any user to evaluate the advantages and drawbacks of the different solutions used.

Note that even if these statistics are specific to a use case, it will still provide a general idea about the performances.

Storage analysis

Storage usage when updating the imx8mqevk from warrior to zeus

This change of version updates the kernel, the ramdisk image, the rootfs, and the device tree. The resulting OSTree commit is about 61MB. This is the amount that the target will have to download for this update.

In this scenario, we will update from warrior to zeus, and then add strace on the target and observe the rootfs storage usage (df -h /) :

Action Yocto df -h / Diff Pulled
- warrior 208.9 MB - -
warrior → zeus zeus 397.9 MB 189 MB 61.0 MB
+ strace zeus 256.8 MB −141.1 MB 388.7 kB

Actions are the steps described in the previous paragraph. Yocto is the release version. df -h / is the storage usage on the target. Diff is the difference between before and after the update in terms of storage usage. Pulled is how much data the client OSTree has pulled.

This table shows that OSTree is great in terms of storage for multiple reasons :

  • the update are deltas updates, meaning that only updated packages are actually shipped in the update
  • OSTree's repositories features clearly show here as we take advantage of the archive repo to optimize the data we have to download
  • OSTree only keeps the last two commits in storage, meaning that the target storage will not continuously increase

Note that if the updates fails, the system can still rollback even if the full system is upgraded.

Storage usage when updating the imx8mqevk from warrior to dunfell

This time, we see what an update from warrior to dunfell takes on the imx8mqevk.

Action Yocto df -h / Diff Pulled
- warrior 194.0 MB - -
warrior → dunfell dunfell 413.3 MB 219.3 MB 64.5 MB
+ strace dunfell 247.8 MB -165.5 MB 394.6 kB

As we can see, there not much of a difference compared to a transition from warrior to zeus as we have seen in the previous section.

We could positively say that the update gap between version of Yocto should be approximatively constant - depending on what is installed on the target of course.