Quoting Michael Biebl (bi...@debian.org):
> Am 04.06.2015 um 06:59 schrieb David Wright:
> > $ systemd-analyze blame
> > 1min 13.144s acpi-support.service
>
> Can you please try and uninstall and purge
> the following packages (not typically needed with jessie anyway)
>
> acpid
> acpi-support-base
> acpi-support
> consolekit
I've purged (in three tranches):
[REMOVE, NOT USED] acpi-fakekey:i386
[REMOVE, NOT USED] libck-connector0:i386
[REMOVE, NOT USED] libpam-ck-connector:i386
[REMOVE] acpi-support:i386
[REMOVE] acpi-support-base:i386
[REMOVE] acpid:i386
[REMOVE] avahi-autoipd:i386
[REMOVE] avahi-daemon:i386
[REMOVE, NOT USED] libavahi-core7:i386
[REMOVE, NOT USED] libdaemon0:i386
[REMOVE] modemmanager:i386
but the resulting timings are not encouraging: 74 to login,
30 to bash prompt, 62 for X.
After the third tranche:
$ systemd-analyze blame
36.727s wicd.service
22.102s binfmt-support.service
20.789s alsa-restore.service
20.618s lm-sensors.service
20.565s systemd-logind.service
20.471s rsyslog.service
20.468s rc-local.service
20.465s systemd-user-sessions.service
20.462s apmd.service
20.461s virtualbox.service
20.461s loadcpufreq.service
20.460s gpm.service
20.135s bluetooth.service
19.730s exim4.service
11.922s timidity.service
6.523s ntp.service
5.925s colord.service
4.376s kbd.service
4.109s networking.service
3.461s systemd-tmpfiles-setup-dev.service
3.400s systemd-modules-load.service
3.257s systemd-fsck@dev-disk-by\x2dlabel-john03.service
3.215s keyboard-setup.service
3.027s systemd-fsck@dev-disk-by\x2dlabel-john02.service
2.947s irqbalance.service
2.775s nfs-common.service
2.600s systemd-tmpfiles-setup.service
2.215s rpcbind.service
1.900s dev-hugepages.mount
1.808s dev-mqueue.mount
1.788s resolvconf.service
1.773s hdparm.service
1.753s westw.mount
1.738s sys-kernel-debug.mount
1.428s systemd-journal-flush.service
1.420s systemd-setup-dgram-qlen.service
1.226s user@1000.service
1.167s cpufrequtils.service
1.145s systemd-udev-trigger.service
1.013s aumix.service
927ms gdomap.service
828ms saned.service
658ms kmod-static-nodes.service
521ms dev-disk-by\x2dlabel-john04.swap
486ms systemd-update-utmp.service
381ms systemd-udevd.service
366ms systemd-backlight@backlight:intel_backlight.service
310ms systemd-rfkill@rfkill2.service
310ms systemd-rfkill@rfkill1.service
310ms systemd-rfkill@rfkill0.service
287ms systemd-sysctl.service
241ms home.mount
218ms systemd-backlight@backlight:dell_backlight.service
195ms clamav-daemon.socket
178ms systemd-random-seed.service
108ms console-setup.service
65ms systemd-remount-fs.service
52ms systemd-rfkill@rfkill3.service
47ms udev-finish.service
18ms proc-sys-fs-binfmt_misc.mount
8ms systemd-update-utmp-runlevel.service
3ms sys-fs-fuse-connections.mount
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1min 17.390s
└─multi-user.target @1min 17.390s
└─exim4.service @57.659s +19.730s
└─clamav-daemon.service @57.652s
└─basic.target @36.880s
└─sockets.target @36.877s
└─clamav-daemon.socket @36.678s +195ms
└─sysinit.target @36.671s
└─nfs-common.service @33.893s +2.775s
└─rpcbind.target @33.886s
└─rpcbind.service @31.667s +2.215s
└─network-online.target @31.661s
└─network.target @31.657s
└─networking.service @27.545s +4.109s
└─local-fs.target @27.522s
└─run-rpc_pipefs.mount @36.015s
└─local-fs-pre.target @12.226s
└─systemd-remount-fs.service @12.152s +65ms
└─keyboard-setup.service @8.928s +3.215s
└─systemd-udevd.service @8.537s +381ms
└─systemd-tmpfiles-setup-dev.service
@5.073s +3.461s
└─kmod-static-nodes.service @4.412s
+658ms
└─system.slice @4.406s
└─-.slice @4.405s
I've tried to analyse the Login-BashPrompt time of 30-34 secs.
I added set -v to the start of .bash_profile and the end of .bashrc,
and set +v to the start of .bashrc and the end of .bash_profile,
ie excluding tracing .bashrc because it lists every function
as they are defined.
What I discovered is that .bash_profile is reached 16 seconds after
"You have new mail." and that a function which copies a lot of my
startup files to /tmp/.my-startups/ takes over 15 seconds to run.
(The disk activity light is lit through the entire boot/login process
and beyond.)
If I wait a while and then delete /tmp/.my-startups/ and rerun
that function, there is no perceptible pause. There are 57 files
with a total size of 383901 bytes.
I also timed X starting up. In wheezy, the screen blanks after a few
seconds and the (wristwatch) cursor appears at 9 seconds, just beating
the root screen. In jessie, the screen blanks after 15 seconds and the
root screen and cursor appear at 45 seconds.
Note that, like everything else, X will start up much more quickly
on subsequent occasions, wheezy still beating jessie.
Running emacs in X (ie windowed, and long after disk activity has
ceased), on the first occasion emacs is run, the window is mapped
after 4 (wheezy) / 12 (jessie) seconds.
Cheers,
David.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150604191029.GA16465@alum
