This project aims to make a brief benchmark of the memory footprint of the F' framework to get an idea of it.

In order to evaluate the memory footprint of F´ we simplified the reference deployment topology "Ref", which we replicated in "App" and then simplified. The metrics considered relevant to evaluate the minimum size of F´ are:

• the size of the .text/.rodata/.data/.bss sections of the binary
• the size of the ELF
• the size of the binary from the ELF by the command objcopy -O binary App App.bin.

Initially we measured these artifacts only by customizing some symbols dimensioning the compiled code of the framework. Let's say:

• FW_OBJECT_NAMES,
• FW_OBJECT_REGISTRATION,
• FW_PORT_TRACING,
• FW_ENABLE_TEXT_LOGGING,
• FW_SERIALIZABLE_TO_STRING,
• FW_PORT_SERIALIZATION.

So notice that we didn't play with the options passed to the compiler or the linker at all. In fact, no options are passed to both, except for warnings to the compiler.

For more information, see the note on the configuration of F´ available in the project documentation: fprime/docs/UsersGuide/dev/configuring-fprime.md

All measurements were made with GNU 10.3.0 at commit 7890e7d of the project, which is the 4900th commit 😁.

We proceeded in 7 steps, the step n repeats the same configurations as the previous step n-1 to which we add a delta by deactivating a previously activated symbol.

Regarding the options passed to the toolchain, i.e. the compiler and the linker, we did not see any real difference compared to the measurements obtained in step 7. Only the linker option in step 5 subtly reduces the footprint - insignificant. We marked "x" when the value did not change.