[lubuntu-users] LUBUNTU 16.xx, 17.xx, 18.xx, VERY SLOW BOOT...! Damaged Product=

[Walter Lapchynski]

Since you made this post to the mailing list, I'm including it back in
it. Please reply all so we can all be involved in the conversation.

> On Fri, Nov 9, 2018 at 11:35 AM Walter Lapchynski <wxl at ubuntu.com> wrote:
> > On Sun, Nov 04, 2018 at 07:26:31PM +0700, Kopi Tv wrote:
On Sat, Nov 10, 2018 at 04:53:05PM +0700, Kopi Tv wrote:

> > > LUBUNTU 16.xx, 17.xx, 18.xx, VERY SLOW BOOT...! =
> > Compared to?
> Compared to Lubuntu/Ubuntu 14.04 (14.04 is the best Product)

I think it's erroneous to assume that software will simply remain the
same. Also, it would be erroneous to assume that Lubuntu wouldn't be
caught by the same changes shaping Ubuntu, at least on some level. We're
not using the same desktop interface, but we are using the same kernel.
We're also using the same init system. This is particulary relevant as
16.04 was the first LTS release that used systemd.

systemd is something that we could spend hours writing about pros and
cons of. In fact, it's been something of a holy war in the world of
Linux. Far too much time has been wasted arguing about the pros and cons
of it. The reality of it is that, for Lubuntu, since Ubuntu is using it,
we're using it. And that means we're mostly at the whims of what Ubuntu
decides to do with regards to configuration.

However, one should note that unlike the previous init system, systemd
is lazy or dependency-based, which is like saying it doesn't load things
until needed. Oddly, this can mean that sometimes if a service is not
loaded as early as possible, the *overall* boot time can be increased.

Which gets at another thing: you can affect the system and customize it
for yourself. The first part of that is analyzing things. You can find
out a little bit about that here:
https://www.dedoimedo.com/computers/systemd-blame.html
https://wiki.freedesktop.org/www/Software/systemd/Optimizations/

The other thing I'll mention is that since Lubuntu has historically been
focused on limiting resource use as much as possible, we have used zram.
However, because of a bug in initramfs, boot times were increaed
because of this. We plan on fixing this in 18.04 and so on, but
meanwhile you can use the manual workaround mentioned there if you are
affected:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1781746

-- 
       @wxl | polka.bike
C563 CAC5 8BE1 2F22 A49D 
68F6 8B57 A48B C4F2 051A