Which Background Services To Disable Kubuntu

More and more operating systems become bloated with lots of services that run in the groundwork. While they may not apply much CPU fourth dimension, they increase boot fourth dimension and RAM usage.

Some Linux distributions include "everything just the kitchen sink," in an effort to make user life easier. This makes things such every bit file sharing or printing work out of the box. Unfortunately, the only style to do this is to include hundreds of utilities so that anybody finds something they need.

Fortunately though, open up-source operating systems give you the power and freedom to do as you encounter fit. This means y'all can disable or remove anything you don't need. The first pick, how to disable services, will be explored here. When you disable, rather then remove, components, there's less run a risk of permanently breaking things. And you can go back to the way it was earlier by merely re-enabling a service if you observe something useful stopped working.

Analyze the Time It Takes for Each Service to Load

Well-nigh Linux-based operating systems accept migrated to Systemd. Amid the suite of utilities it includes, there is a program that lets you analyze how fast your arrangement boots. Specifically, information technology shows yous the total time required to boot and the fourth dimension it takes for each service to load. Note that some services load in parallel. And then, if one requires two seconds to load and the other iii seconds, information technology doesn't necessarily mean five seconds are required in total. Information technology may be much less than that.

Open up a terminal emulator and enter this command:

This shows how long it takes for the Linux kernel and base system services to load, which means it doesn't account for the fourth dimension your graphical interface requires to boot up. To put it another fashion, this shows y'all how much time is required, from the moment the kernel is loaded until you are dropped to the Linux console, which looks like what is depicted below.

If yous didn't have a graphical interface installed, this is what you would be greeted with on your screen.

However, you tin can also see the fourth dimension required past the graphical interface to initialize with this command:

systemd-clarify disquisitional-chain graphical.target

This shows that the graphical user interface loaded in 2.126 seconds. This doesn't account for the time required to load desktop utilities. To enable/disable those, launch your desktop environment startup manager.

Finally, probably the most useful command for the purpose of this tutorial is:

You can navigate the list with your arrow keys or PAGE Upwardly and Page DOWN. Press q to quit.

Use systemctl to Disable Unnecessary Services

As you lot tin see in the previous moving picture, the snapd service takes i.295 seconds to load. On an SSD, this is negligible. But on a difficult deejay, these kinds of times would be in the orders of multiple seconds, and they would add together upward to a lot in the end. Also, on an SSD many things load in parallel with incredible efficiency. On a hard disk drive it's very hard for services to load in parallel. The read heads that float on the deejay platters have to move from sector to sector, and then it's nigh incommunicable to truly read information in parallel.

To simplify, imagine this: if on an SSD you lot would run across v services that require one 2nd to boot, information technology's likely that the total time required to load all of these might exist less than 1.2 seconds. If, on a hard disk drive, you run into the same five services initialize in one second, it's likely that the total load fourth dimension is way higher up five seconds.

Say you lot don't need the snapd service, which provides admission to containerized awarding snaps. You can disable it with this command:

            sudo            systemctl disable snapd.service

But, if you reboot, you volition detect the snap daemon is even so running. That'due south because other dependencies may launch it, even if it's disabled. Attempt to see what those may be:

systemd-clarify arraign            |            grep            snap

snapd.seeded.service and snapd.socket are the culprits hither. A kid service can asking to launch its parent service. When you disable one, you but tell information technology to not automatically start at boot by itself. But there is a brute-forcefulness method to go effectually this result.

Utilise systemctl to Mask a Service

            sudo            systemctl mask snapd.service

This basically makes the service file null so that applications have no way to start the service.

In most cases it's non this complicated to disable a service. This example has been called to evidence yous how to bargain with trickier scenarios. In this example, snapd.seeded.service and snapd.socket should exist disabled or masked, too.

The post-obit shows the improved boot time.

Conclusion

From iv.078, boot fourth dimension was reduced to three.452 seconds, which amounts to a subtract of ~15%. Not also bad, because merely ane service was disabled, and this is on an SSD. On a hard disk it's much easier to get much more than significant results.

In this particular case, more services could have been disabled with a control similar: sudo systemctl mask avahi-daemon.service ModemManager.service thermald.service pppd-dns.service.

If you adopt a graphical application to manage your services, you lot can take a look at the Systemd Managing director project. You will exist limited in what yous tin do with it, though, since the control line offers much more flexibility.

Is this article useful?

Subscribe to our newsletter!

Our latest tutorials delivered straight to your inbox