According to `systemd-analyze blame`  Accounts Service takes over half a second to initialize.
$ systemd-analyze blame
This is pretty long compared to other processes, though the output only says how long the processes take to register themselves on the D-Bus(?) (or something like it).
Still it should not take that long to start and hopefully the code can be optimized.
Half a second does not sound much to some, but for a fast boot (less than three seconds) it is essential that each process takes as little time as possible.
 $ man systemd-analyze
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 critical-chain # with Network Manager disabled
└─accounts-daemon.service @1.046s +456ms
└─console-setup.service @1.036s +2ms
└─kbd.service @701ms +334ms
└─boot.mount @593ms +104ms
(In reply to Paul Menzel from comment #0)
> Still it should not take that long to start and hopefully the code can be
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/21.