WHY is this OS so SUPER SLOW??

Questions specific to the KDE DE go here
Ronny
Posts: 4
Joined: 11 Jul 2018 23:07

WHY is this OS so SUPER SLOW??

Postby Ronny » 11 Jul 2018 23:19

If this is a Mint based OS... I just don't understand why it is so SLOW!!

I am running this on a Dell 15 3000 laptop with an i5 and 8 gb ram
with TB HDD. I also tried this on my Dell desktop computer and
same thing. I spoke to a YouTube reviewer of Linux distros and
he too said he refuses to run this OS due to the extreme slowness
of it. What is UP??

User avatar
tek10
Posts: 29
Joined: 30 Jul 2013 01:22
Location: Cascadia

Re: WHY is this OS so SUPER SLOW??

Postby tek10 » 12 Jul 2018 03:29

A minor point first, SolydK is based on Debian Stable rather than Mint.

I'm running SolydK on an older system using an AMD A10-5800K with 8 GB RAM and a hybrid hard drive, not even an ssd. It performs very smooth and fast for me. For example, after starting up the system today I ran an analysis:

$ systemd-analyze
Startup finished in 9.410s (kernel) + 14.325s (userspace) = 23.736s
graphical.target reached after 14.294s in userspace

While not as fast as my Manjaro KDE system running an i5 processor with 16GB RAM, I don't really see much difference in daily performance between the two systems. Maybe there are some settings that can be adjusted to speed up your system?

Another idea might be to try SolydX using xfce rather than KDE. I'm running that on a nine year old HP laptop with a Pentium A4200 and 3GB RAM and it's very fast and stable.

User avatar
Arjen Balfoort
Site Admin
Posts: 8860
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: WHY is this OS so SUPER SLOW??

Postby Arjen Balfoort » 12 Jul 2018 06:43

Indeed, SolydXK is not based on Mint but on Debian.

Performance issues can be analyzed by these commands:

Code: Select all

systemd-analyze
systemd-analyze critical-chain
systemd-analyze blame
For my 6 year old system with SolydK it looks like this:

Code: Select all

arjen@solydxk_main:~$ systemd-analyze
Startup finished in 6.011s (firmware) + 7.584s (loader) + 8.228s (kernel) + 16.956s (userspace) = 38.780s
arjen@solydxk_main:~$ 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 @16.949s
└─multi-user.target @16.949s
  └─smbd.service @16.852s +96ms
    └─nmbd.service @6.778s +10.071s
      └─network-online.target @6.775s
        └─NetworkManager-wait-online.service @1.316s +5.459s
          └─NetworkManager.service @1.174s +140ms
            └─dbus.service @1.065s
              └─basic.target @1.060s
                └─paths.target @1.060s
                  └─acpid.path @1.060s
                    └─sysinit.target @1.059s
                      └─sys-fs-fuse-connections.mount @3.610s +2ms
                        └─systemd-modules-load.service @202ms +62ms
                          └─system.slice @201ms
                            └─-.slice @176ms
arjen@solydxk_main:~$ systemd-analyze blame
         10.071s nmbd.service
          5.459s NetworkManager-wait-online.service
          2.661s solydxk-system-adjust.service
          1.522s apt-daily.service
          1.231s set-doc-permissions.service
           691ms apt-daily-upgrade.service
Where you can see that nmbd.service is taking a long time. In my case that can be explained by two external samba shares that are being mounted in fstab.
Every system is different. If you want to know what's causing the delay on your system, you can use these three commands and post back your finding here.


SolydXK needs you!
Development | Testing | Translations


Return to “KDE specific (SolydK)”

Who is online

Users browsing this forum: No registered users and 0 guests