24

publicado de forma cruzada desde: https://lemmy.ca/post/7400605

So I jumped ship from Windows to Kubuntu last night, and It's mostly been pretty good. However my general performance of the computer has been abysmal. Like it takes upwards of 5 seconds to open anything. All of my hardware seems to be running at max speeds, so I have no idea why it would be so sluggish? It's as if I'm running on 2gb of ram and a cpu at like 1.5ghz. My specs are:

i7-8700k at 4.7mhz max Amd Rx 6750xt 16gb ram at 3200mhz Linux is on an m.2

Any ideas? This is practically unusable for any normal operations, let alone any gaming.

top 28 comments
sorted by: hot top controversial new old
[-] Pantherina@feddit.de 28 points 1 year ago* (last edited 1 year ago)

Hahahaha welcome to Snaps.

Get rid of Kubuntu is what I would recommend. Really.

Question, do you want to do crazy stuff? Do you want A LOT more than what you find on Flathub.org ?

If not, and you want a fast and stable system, get Fedora Kinoite, you may want to use Universalblue Images to have Firefox and all the rest working (videocodecs installed and automatic updates mostly. If you have NVIDIA you NEED the ublue kinoite-nvidia image)

On Fedora you just need to disable fedora flatpaks, enable flathub, install your apps and voila.

Follow the flathub.org Setup instructions, in Discover you can set the sources and disable Fedora Flatpaks.

I am working on a GUI setup script to fix everything.

[-] lupec@lemm.ee 3 points 1 year ago

If OP is also interested in gaming, Bazzite is another great ublue-based choice. I've been daily driving it for a while on my Deck and it works beautifully. User friendly setup and low maintenance but has plenty of useful knobs power users can tweak.

[-] Pantherina@feddit.de 4 points 1 year ago

Exactly.

So as an explanation, Fedora Atomic is like Git for your OS. This means the OS keeps track of every package, what is where etc. On the server lays a fresh, recent image, assembled by the Fedora people. They ship really recent software and these images are well tested and should just work.

This is exactly the state you have on a regular Distro, after installing the ISO (and nothing went wrong). But what happens now? You install, uninstall, move, compile, write stuff to system directories, etc.

In the end we have 100 Ubuntu users with 100 different systems. "I have this issue but nobody else has it", yes because your system is unique and you have no idea why.

Meanwhile Android does the exact opposite, since forever. And that sucks. But as apps are highly confined and the system is read-only (lol often not even readable) you have no viruses.

Fedora Atomic with rpm-ostree does a thing in between. You have your Operating system, good as it is. But in Fedora for example there are Codecs missing so Firefox or direct Binaries like Davinci Resolve will give you a hard time.

You can "layer" packages though, that means from then on you have the official image plus a transparent set of extra packages. If you find out this breaks something, do rpm-ostree uninstall PACKAGE and that layer is gone.

If you want to reset your system entirely, do rpm-ostree reset (this is not android-level yet, you still need to remove /var /etc and more.)

Also there are containers. They are not virtual machines because they use your systems kernel. But you can install all those nasty dependencies you need for example for that one old app, for building software etc. Using Toolbox or Distrobox this is really easy.

So before modifying the system, you can use that instead. Still, you can modify your system a lot, add repos, etc.

Then comes universalBlue. They do the modifying BEFORE sending the images to your client. So the modifications are not your own, and errors may already be discovered when you would get them. Also, having the changes there reduces the load on your machine, all you do is download, build, reboot, done. Automatically.

This is so much better than Windowd Updates, more secure and with no boot delay AT ALL. That fact alone is a crazy selling point.

If you ask yourself "why should I need this", just think about how your OS will look like in 5 years. So many changes, but using rpm-ostree you are always just one command away from having a "fresh install" experience.

[-] lupec@lemm.ee 3 points 1 year ago

Incredible tech huh? I'd toyed with the idea of immutable distros before with NixOS but found it a bit too restrictive so Kinoite and co are exactly the middle ground I was looking for.

With Bazzite specifically, I get a pretty damn up to date Fedora base, most of the annoying kernel/gaming things I want but don't want to mess with by default and also Nix + distrobox out of the box for development environments and some wiggle room for whatever I can't natively install. Just a great experience all around.

[-] Pantherina@feddit.de 2 points 1 year ago
[-] lupec@lemm.ee 2 points 1 year ago* (last edited 1 year ago)

Yup! I've deployed my Home Manager config on my install with no issues.

[-] klangcola@reddthat.com 2 points 1 year ago

Thanks for the thorough explanation, Fedora atomic, os-tree and Universal blue is such a new and different way of thinking about the OS compared to the traditional desktop installs. It's also a lot of new jargon so thanks for taking the time to explain each component

[-] Jerry1098@sh.itjust.works 1 points 1 year ago

Do you or anyone else know how MicroOS compares to that? I know that it's mostly the same technology and I preferred Tumbleweed over Fedora Workstation

[-] Pantherina@feddit.de 2 points 1 year ago

As far as I understood its worse, as they dont use OSTree but BTRFS snapshots. So they have an image, do atomic updates from some repository (not sure how thats done) and then build the next image. This process is atomic as a fail will cancel the update.

But the fetching or things is done via a normal package manager, its just building differently on your machine, again, aa far as I understood.

Then you have BTRFS snapshots which you reboot into. You can also layer packages, not sure how that is done and if its reversible.

[-] mkwt@lemmy.world 14 points 1 year ago

Just a guess: you might actually be running the CPU at a low frequency. As in the frequency scaling driver isn't working.

Maybe poke around on a performance monitor tool. Seems like there's "Plasma System Monitor" on KDE. Make sure the tool can see all the RAM, all of the CPU cores (2x physical cores with Intel hyper threading).

It should also report the CPU frequency, which should go up and down depending on the load. You can also check that the CPU temperature report is reasonable.

This also gives you process info, so when one of these 5 second freezes happens, you should be able to see what shoots to the top of the list. Or maybe there's a background task churning through a bunch of stuff. Or maybe the flash access is really slow.

[-] Canadian_Cabinet@lemmy.ca 19 points 1 year ago

This is it. CPU is throttling itself due to high temps. Not i just need to figure out why it's so hot

[-] captainlezbian@lemmy.world 7 points 1 year ago

Is your cooling system on?

[-] JustEnoughDucks@feddit.nl 4 points 1 year ago

Hot CPU?

Is the CPU fan running?

Is CPU usage stuck high?

A lot of dust in the cooler fins?

Is it a stock CPU or aftermarket?

Is the plastic sticker off of the CPU cooler?

Enough thermal paste on the CPU?

Screws tightened down enough on CPU cooler?

That's pretty much the order of diagnosing CPU air cooler problems lol

[-] i_cant_sports@lemmy.ml 2 points 1 year ago

Screws tightened down enough on CPU cooler?

Or tightened too much? And/or unevenly?

[-] Cornelius@lemmy.ml 9 points 1 year ago

Why is this getting down voted? It's a genuine ask for help :/

[-] klangcola@reddthat.com 7 points 1 year ago

In addition to the CPU throttling itself due to thermals like you said, you should also be aware that all Ubuntu's are replacing more and more traditional packages with snaps for an increasing number of applications.

Step 1 (by the system) of opening a snap application for the first time (since boot) is to extract the compressed snap image, which makes startup time significantly longer (like several seconds for something you would expect to be instant). Once the application is started performance should be the same as if the application had been installed as a traditional .deb package.

You should also consider adding flatpak support and flathub. Applications installed as Flatpaks generally integrate better in the desktop than snaps, and flathub has a large and growing selection of apps. The flathub website has a few command lines you can copy-paste to enable flatpak and flathub support, then apps from Flathub will show up in the Discover app store.

Personally I use Kubuntu and use both Flatpak and snap apps, but generally prefer flatpaks when they're available. And any software where I don't care about having a recent version I install as a traditional package because it's more lean

[-] DmMacniel@feddit.de 6 points 1 year ago

Welcome to snaptown where everything is slow at first. Please consider not using a canonical Linux distribution (Ubuntu, Kubuntu, Xubuntu, Ubuntu Studio). So something like Linux Mint, Fedora Linux.

You said you want to do gaming? Consider Garuda Linux (with KDE flavour) or Nobara Linux (Gnome flavour) those are aimed for gaming but supports everything else as well.

Snaps are only really useful on Server Machines and I don't know why, canonical is pushing this so hard.

[-] spudwart@spudwart.com 2 points 1 year ago

If this isn't your first round on linux, Try Debian, set it to use non-free contrib packages and set the appstore to install apps as flatpaks before native.

Avoid using Ubuntu based distros as they run Snap packages which are just a general nightmare for users.

Snaps make sense for servers, but the only reason Ubuntu forces it on users is $$$$.

[-] infeeeee@lemm.ee 2 points 1 year ago

THe good thing with linux, that it's totally transparent, you can easily find what's wrong, if you look at the right place.

First I would check journalctl, dmesg, running processes with htop, if I can see something wrong, unexpected. Check hard drive smart and run short selft test with gsmartcontrol.

Here is a general troubleshooting guide from arch wiki: https://wiki.archlinux.org/title/General_troubleshooting I know you use ubuntu, but most of the commands here are the same on all distros, basically anything not related to pacman should be the same on your system

Ubuntu wiki has a similar guide, but shorter, guide, maybe start here: https://help.ubuntu.com/community/TroubleShootingGuide

[-] HumanPerson@sh.itjust.works 1 points 1 year ago

This sounds like a slow drive except you said it's on an m.2. If you just switched recently enough that this wouldn't be a major inconvenience, I would try a different distro. You haven't said anything about your use case, so I can't make a specific recommendation, but distrochooser.de could help with that.

[-] s12@sopuli.xyz 1 points 1 year ago* (last edited 1 year ago)

I had this problem too.

The issue for me was that my computer had two disks, a small fast one (sata ssd) and a large slow one. Windows had separated itself with the operating system itself and installed programs on the ssd, with all user documents on the slow disk.

Linux can do this too. Put a partition mounted on / (root) on the fast disk, and one mounted on /home on the large disk.

I’d put both on the large disc initially.

There’s a part of the installation where you set up the partitioning. Redoing the installation really sped up my Linux Mint installation.

[-] Canadian_Cabinet@lemmy.ca 2 points 1 year ago

The way I currently have it is that I have Windows on a SATA SSD and Kubuntu on a M.2. Windows doesn't know about the Linux M.2 but Linux knows about the Windows SSD

this post was submitted on 18 Oct 2023
24 points (74.0% liked)

Linux Gaming

15910 readers
4 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS