Feature #12318

Have our test suite track detailed boot-up performance

Added by intrigeri 2017-03-11 12:24:37 . Updated 2019-09-30 08:06:22 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
2017-03-11
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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.

Subtasks

Related issues

Related to Tails - Feature #11971: Consider migrating some of /lib/live/config/* to systemd unit files Resolved 2016-11-20
Related to Tails - Bug #9097: Automatic test: measure boot time Confirmed 2015-03-23

History

#1 Updated by anonym 2017-03-12 18:49:22

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 step) the 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 2017-03-13 07:09:25

> 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.

#3 Updated by intrigeri 2017-03-13 15:45:27

  • related to Feature #11971: Consider migrating some of /lib/live/config/* to systemd unit files added

#4 Updated by intrigeri 2017-03-13 15:51:55

For example, having this would give us the data we need to decide whether there’s something to be done on Feature #11971.

#5 Updated by intrigeri 2017-06-05 15:36:29

Hi spriver! If you’re looking for not-too-hard new test cases we need in order to get some training, this could be a good candidate. Feel free to steal it from me.

#6 Updated by spriver 2017-06-05 16:02:03

  • Assignee changed from intrigeri to spriver

Seems like a doable thing for the next weeks for me (:

#7 Updated by Anonymous 2018-01-16 09:41:15

Hi spriver, are you still interested in working on this? If yes, fine. If no, you could reassign it to intrigeri.

#8 Updated by intrigeri 2019-08-30 10:28:10

  • related to Bug #9097: Automatic test: measure boot time added

#9 Updated by intrigeri 2019-09-30 08:06:22

  • Assignee deleted (spriver)

(I’ve discussed this with spriver out-of-band. Conclusion: anyone should feel free to take this ticket if they’d like to.)