difference in Mint 19.3 and 20

[deepakdeshp]

Dual boot Mint 19.3 and Mint 20. Mint 19.3 takes 2 minutes 35 seconds to boot , Mint 20 1 minute 20 seconds. Mint 20 is a fresh install without any extra applications installed while in 19.3 I have installed many applications. Is this the problem?

Mint 19.3 free memory 5.3 GB 5.9 gb. This is without starting any application.

[senjoz]

I have LM 20 cinnamon and LM 19.3 cinnamon installed on the same nvme SSD disk. Below are my boot times according to systemd-analyze. Maybe it is time that you upgrade your disk.

Code: Select all

lm 20 cinnamon
@flbu727:~$ systemd-analyze
Startup finished in 5.348s (firmware) + 2.695s (loader) + 3.512s (kernel) + 3.425s (userspace) = 14.981s 
graphical.target reached after 2.964s in userspace
@flbu727:~$ free
              total        used        free      shared  buff/cache   available
Mem:       16221940      557112    14920776      104832      744052    15277916
Swap:       1551124           0     1551124


lm 19.3 cinnamon
@flbu727:~$ systemd-analyze
Startup finished in 5.364s (firmware) + 3.223s (loader) + 4.385s (kernel) + 1.736s (userspace) = 14.710s
graphical.target reached after 1.498s in userspace
@flbu727:~$ free
              total        used        free      shared  buff/cache   available
Mem:       16221964      458928    15242856      102236      520180    15386236
Swap:       1551124           0     1551124

Regards,
Jože

[deepakdeshp]

I have LM 20 cinnamon and LM 19.3 cinnamon installed on the same nvme SSD disk. Below are my boot times according to systemd-analyze. Maybe it is time that you upgrade your disk.

Code: Select all

lm 20 cinnamon
@flbu727:~$ systemd-analyze
Startup finished in 5.348s (firmware) + 2.695s (loader) + 3.512s (kernel) + 3.425s (userspace) = 14.981s 
graphical.target reached after 2.964s in userspace
@flbu727:~$ free
              total        used        free      shared  buff/cache   available
Mem:       16221940      557112    14920776      104832      744052    15277916
Swap:       1551124           0     1551124


lm 19.3 cinnamon
@flbu727:~$ systemd-analyze
Startup finished in 5.364s (firmware) + 3.223s (loader) + 4.385s (kernel) + 1.736s (userspace) = 14.710s
graphical.target reached after 1.498s in userspace
@flbu727:~$ free
              total        used        free      shared  buff/cache   available
Mem:       16221964      458928    15242856      102236      520180    15386236
Swap:       1551124           0     1551124

Regards,
Jože

Your start times for both systems are almost same, in my case start system of 19.3 is twice that of LM 20.

[senjoz]

Try with:

Code: Select all

systemd-analyze blame

or

Code: Select all

systemd-analyze critical-chain

Maybe you will see where the problem is.

Regards,
Jože

[smurphos]

Mint 19.3 free memory 5.3 GB 5.9 gb. This is without starting any application.

Is this your 19.3 which has been upgraded in place since 17.something, and has a ton of weird extra services running, and which dies every time you try and clean out residual config (upsetting DAMIEN1307 in the process - )

That'll be the reason why. Time for a nuke and pave.

[all41]

Dual boot Mint 19.3 and Mint 20. Mint 19.3 takes 2 minutes 35 seconds to boot , Mint 20 1 minute 20 seconds.

imho these are terrible boot times--even using hdd.
Mostly I see 18-24 seconds on hdd, but with ssd about 9.2 seconds for a well populated and used Mint 19.3 MATE,
and 7.3 seconds for a freshly installed Mint 20 MATE
My inxi:

Code: Select all

$ inxi -Fxz
System:    Host: labonline Kernel: 5.4.0-39-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: MATE 1.22.2 
           Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop System: LENOVO product: 4157D51 v: ThinkStation S20 serial: <filter> 
           Mobo: LENOVO model: LENOVO serial: <filter> BIOS: LENOVO v: 60KT47AUS date: 01/15/2014 
CPU:       Topology: Quad Core model: Intel Xeon W3550 bits: 64 type: MT MCP arch: Nehalem rev: 5 L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 48943 
           Speed: 2055 MHz min/max: 1596/3060 MHz Core speeds (MHz): 1: 1616 2: 1598 3: 1649 4: 1614 5: 1682 6: 1602 7: 1672 
           8: 1621 
Graphics:  Device-1: NVIDIA G96GL [Quadro FX 580] driver: nouveau v: kernel bus ID: 02:00.0 
           Display: x11 server: X.Org 1.19.6 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: NV96 v: 3.3 Mesa 19.2.8 direct render: Yes 
Audio:     Device-1: Intel 82801JI HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k5.4.0-39-generic 
Network:   Device-1: Intel 82574L Gigabit Network driver: e1000e v: 3.2.6-k port: 3000 bus ID: 04:00.0 
           IF: ens1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Broadcom and subsidiaries NetXtreme BCM5755 Gigabit Ethernet PCI Express vendor: Lenovo driver: tg3 
           v: 3.137 port: 3000 bus ID: 05:00.0 
           IF: ens5 state: down mac: <filter> 
Drives:    Local Storage: total: 2.30 TiB used: 228.37 GiB (9.7%) 
           ID-1: /dev/sda vendor: Western Digital model: WD1600HLFS-75G6U1 size: 149.01 GiB 
           ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB 
           ID-3: /dev/sdc vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
           ID-4: /dev/sdd vendor: PNY model: CS900 120GB SSD size: 111.79 GiB 
Partition: ID-1: / size: 29.21 GiB used: 12.66 GiB (43.3%) fs: ext4 dev: /dev/sdb1 
           ID-2: /home size: 113.17 GiB used: 2.37 GiB (2.1%) fs: ext4 dev: /dev/sdb6 
           ID-3: swap-1 size: 3.72 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb5 
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: nouveau temp: 52 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 0 
Info:      Processes: 238 Uptime: 3h 54m Memory: 15.63 GiB used: 2.07 GiB (13.3%) Init: systemd runlevel: 5 Compilers: 
           gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 

This system is 9ish years old and came with W7.

[senjoz]

imho these are terrible boot times--even using hdd.
Mostly I see 18-24 seconds on hdd, but with ssd about 9.2 seconds for a well populated and used Mint 19.3 MATE,
and 7.3 seconds for a freshly installed Mint 20 MATE
This system is 9ish years old and came with W7.

Qute short boot times for the nine years old system. How you measured 7.3 seconds. Can you post output of systemd-analyze?

Regards,
Jože

[deepakdeshp]

Mint 19.3 free memory 5.3 GB 5.9 gb. This is without starting any application.

Is this your 19.3 which has been upgraded in place since 17.something, and has a ton of weird extra services running, and which dies every time you try and clean out residual config (upsetting DAMIEN1307 in the process - )

That'll be the reason why. Time for a nuke and pave.

The machine that was nuked and upset Damien was the same and I have been upgrading it since Mint 17. Will see how my luck holds this time and will the upgrade from 19.3 to 20 break it . If it doesnt, I plan to take the upgrade path.

[all41]

imho these are terrible boot times--even using hdd.
Mostly I see 18-24 seconds on hdd, but with ssd about 9.2 seconds for a well populated and used Mint 19.3 MATE,
and 7.3 seconds for a freshly installed Mint 20 MATE
This system is 9ish years old and came with W7.

Qute short boot times for the nine years old system. How you measured 7.3 seconds. Can you post output of systemd-analyze?

Regards,
Jože

Here they are:
MATE 19.3

Code: Select all

$ systemd-analyze 
Startup finished in 6.190s (kernel) + 3.268s (userspace) = 9.458s
graphical.target reached after 3.259s in userspace

This was installed as a beta when 19.3 was first released and used daily for general pc
and heavy multimedia editing.

MATE 20

Code: Select all

$ systemd-analyze 
Startup finished in 5.793s (kernel) + 1.977s (userspace) = 7.770s 
graphical.target reached after 1.965s in userspace

I added many multimedia apps to lm20 this morning and the boot time has now increased a half-second to 7.77.

[senjoz]

Here they are:
MATE 19.3

Code: Select all

$ systemd-analyze 
Startup finished in 6.190s (kernel) + 3.268s (userspace) = 9.458s
graphical.target reached after 3.259s in userspace

This was installed as a beta when 19.3 was first released and used daily for general pc
and heavy multimedia editing.

MATE 20

Code: Select all

$ systemd-analyze 
Startup finished in 5.793s (kernel) + 1.977s (userspace) = 7.770s 
graphical.target reached after 1.965s in userspace

I added many multimedia apps to lm20 this morning and the boot time has now increased a half-second to 7.77.

I believe you have a bios system and not an efi system. For bios systems systemd-analyze does not count firmware and bootloader times. For efi systems systemd-analyze includes also these times, see my post above. What are your real boot times measured with a stopwatch, from pressing the power button to the login screen?

Regards,
Jože

[deepakdeshp]

Regards,
Jože

I added many multimedia apps to lm20 this morning and the boot time has now increased a half-second to 7.77.

What do you use for photo editing and video editing?

[all41]

Regards,
Jože

I added many multimedia apps to lm20 this morning and the boot time has now increased a half-second to 7.77.

What do you use for photo editing and video editing?

For photo I am using rawtherapee and darktable. Video mostly kdenlive, openshot, some cinelerra and flowblade.

[all41]

Here they are:
MATE 19.3

Code: Select all

$ systemd-analyze 
Startup finished in 6.190s (kernel) + 3.268s (userspace) = 9.458s
graphical.target reached after 3.259s in userspace

This was installed as a beta when 19.3 was first released and used daily for general pc
and heavy multimedia editing.

MATE 20

Code: Select all

$ systemd-analyze 
Startup finished in 5.793s (kernel) + 1.977s (userspace) = 7.770s 
graphical.target reached after 1.965s in userspace

I added many multimedia apps to lm20 this morning and the boot time has now increased a half-second to 7.77.

I believe you have a bios system and not an efi system. For bios systems systemd-analyze does not count firmware and bootloader times. For efi systems systemd-analyze includes also these times, see my post above. What are your real boot times measured with a stopwatch, from pressing the power button to the login screen?

Regards,
Jože

Here is from a system a couple years newer: