systemd-analyzesystemdDeveloperLennartPoetteringlennart@poettering.netsystemd-analyze1systemd-analyzeAnalyze system boot-up performancesystemd-analyze OPTIONS timesystemd-analyze OPTIONS blame systemd-analyze OPTIONS plot > file.svgsystemd-analyze OPTIONS dot Descriptionsystemd-analyze may be used
to determine system boot-up performance of the current
boot.systemd-analyze time
prints the time spent in the kernel before
userspace has been reached, the time spent in the
initial RAM disk (initrd) before normal system
userspace has been reached and the time normal system
userspace took to initialize. Note that these
measurements simply measure the time passed up to the
point where all system services have been spawned, but
not necessarily until they fully finished
initialization or the disk is idle.systemd-analyze blame prints
a list of all running units, ordered by the time they
took to initialize. This information may be used to
optimize boot-up times. Note that the output might be
misleading as the initialization of one service might
be slow simply because it waits for the initialization
of another service to complete.systemd-analyze plot prints
an SVG graphic detailing which system services have
been started at what time, highlighting the time they
spent on initialization.systemd-analyze dot
Generate textual dependency graph description in dot
format for further processing with the GraphViz
dot1
tool. Use a command line like systemd-analyze
dot | dot -Tsvg > systemd.svg to generate
a graphical dependency tree. Unless
or
is passed the generated graph will show both ordering
and requirement dependencies.If no command is passed systemd-analyze
time is implied.OptionsThe following options are understood:Prints a short help
text and exits.Shows performance data
of user sessions instead of the system
manager.When used in
conjunction with the
dot command (see
above), selects which dependencies are
shown in the dependency graph. If
is passed
only dependencies of type
After= or
Before= are
shown. If
is passed only dependencies of type
Requires=,
RequiresOverridable=,
Requisite=,
RequisiteOverridable=,
Wants= and
Conflicts= are
shown. If neither is passed, shows
dependencies of all these
types.Exit statusOn success 0 is returned, a non-zero failure
code otherwise.See Alsosystemd1,
systemctl1