Have our test suite track detailed boot-up performance
It would be useful to have the output of
systemd-analyze plot stored as an artifact, so we can:
- compare boot time between branches
- debug more easily what causes boot-up performance regressions
And while we're at it, saving the output of
systemd-analyze blame and
systemd-analyze critical-chain in
debug.log would be good too.
#1 Updated by anonym about 3 years ago
With risk of stating the obvious: note that Cucumber keeps careful timings of step execution. E.g. the json formatter has a "duration" field for each instance a step is run (only steps as listed in .feature files, not when invoked via the
step method). Of course, we do not always write our steps/features in a way that makes this measurement easy, e.g. in the
I start Tor Browser step we invoke (via
the Tor Browser has started step, so it's not useful there right now, but we could of course change this.
#2 Updated by intrigeri about 3 years ago
With risk of stating the obvious: note that Cucumber keeps careful timings of step execution.
Sure. But Cucumber doesn't know what took time during boot, it can only measure how long it took from the boot menu to the Greeter, and from the Greeter to the GNOME session.