• 10 Posts
  • 345 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle

  • d3Xt3r@lemmy.nztoKDE@lemmy.kde.socialOpt out? Opt in? Opt Green!
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    1 month ago

    I’m not moving any goalposts. You’re the one arguing about the semantics around “Plasma”, and I keep saying that’s irrelevant.

    Refer back to my original comment which was, and I quote:

    So, are there any plans to reduce the bloat in KDE, maybe even make a lightweight version (like LXQt) that’s suitable for older PCs with limited resources?

    To clarify, here I was:

    • Referring to KDE + default apps that are part of a typical KDE installation
    • Stating that a typical KDE installation is bloated compared to a typical lightweight DE like LXQt
    • Saying with the intention that the “bloat” is RELATIVE, with respect to a older PC with limited resources

    The ENTIRE point of my argument was the KDE isn’t really ideal RELATIVELY, for older PCs with limited resources, and I’m using LXQt here are a reference.

    In a subsequent test, here’s a direct apples-to-apples(ish) component comparison:

    Component Process_KDE RAM_KDE Process_LXQt RAM_LXQt
    WM kwin_x11 99 openbox 18
    Terminal konsole 76 qterminal 75
    File Manager Dolphin 135 pcmanfm-qt 80
    File Archiver ark 122 Lxqt-archiver 73
    Text Editor kwrite 121 featherpad 73
    Image Viewer gwenview 129 lximage-qt 76
    Document Viewer okular 128 qpdfview-qt6 51
    Total 810 446

    plasmashell was sitting at 250MB btw in this instance btw.

    The numbers speak for themselves - no one in their right minds would consider KDE (or plasmashell, since you want to be pedantic) to be “light”, in RELATION to an older PC with limited resources - which btw, was the premise of my entire argument. Of course KDE or plasmashell might be considered “light” on a modern system, but not an old PC with 2GB RAM. Whether something is considered light or bloated is always relative, and in this instance, it’s obvious to anyone that KDE/plasmashell isn’t “light”.



  • d3Xt3r@lemmy.nztoKDE@lemmy.kde.socialOpt out? Opt in? Opt Green!
    link
    fedilink
    arrow-up
    11
    arrow-down
    2
    ·
    edit-2
    1 month ago

    You’re arguing semantics and that’s not the point I’m trying to argue here. Forget the term “Plasma”. I don’t really care about what the DE is branded as or what’s in “Plasma” the software package. When I say “KDE”, I mean the desktop + all the basic default/recommended apps that you’d see on a typical KDE installation, such as Dolphin, Konsole, Kate, Kalculator, Spectacle etc that’s part of the KDE project. IDK whether the apps I’ve mentioned are considered part of “Plasma” or not, but again, that’s not the point, I’m saying this is what I meant when I said “KDE” - and what most people would expect when they picture a “KDE” environment.

    Anyways, I tested this myself on two identical VMs with 2GB RAM, one installed with Fedora 40 KDE, and another with Fedora 40 LXQt, both set to use X11 (because LXQt isn’t Wayland ready yet), both updated and running the latest kernel 6.8.10-300.fc40. I logged into the DEs, opened only two terminal windows and nothing else, ran, and ran htop. The screenshot speaks for itself:

    And when I tried disabling swap on both machines, the KDE machine was practically unusable, with only 53MB RAM remaining before it completely froze on me. Meanwhile, the LXQt one was still very much usable even without swap enabled.

    I’d like to see you try running without swap and see how it fares. And if you think it’s unfair disabling swap on a 2GB machine - try installing LXQt yourself, disable swap and see for yourself how much more usable it is compared to KDE.

    And this is why I say KDE is bloated and not suitable for old machines.

    Edit: Also, check out the memory consumption listed by a user in this post: https://lemmy.nz/comment/9070317

    Edit2: Here’s a screenshot of the top 30 processes on my test systems, side-by-side:

    Of the above, I calculated the usage of the top 10 processes specific to each respective DE, and you can see that KDE’s memory usage is almost double that of LXQt. Had I counted all the DE-specific processes, it’d no doubt be a lot more than double.


  • d3Xt3r@lemmy.nztoKDE@lemmy.kde.socialOpt out? Opt in? Opt Green!
    link
    fedilink
    arrow-up
    10
    arrow-down
    3
    ·
    edit-2
    1 month ago

    Correct me if I’m wrong, but this #OptGreen project isn’t talking specifically about Plasma, is it? They don’t mention Plasma anywhere on the page they linked.

    In any case, that’s irrelevant, also, I don’t doubt that KDE can’t run at all under the specs you mentioned - that’s not the issue. The question is, how much free/usable RAM do you actually have on that machine - let’s say with no apps open first, and with then check again with Konsole + Dolphin + KWrite/Kate open? And for fun, fire up Konqueror as well and check again.


  • d3Xt3r@lemmy.nztoKDE@lemmy.kde.socialOpt out? Opt in? Opt Green!
    link
    fedilink
    arrow-up
    15
    arrow-down
    6
    ·
    edit-2
    1 month ago

    Edit: Screenshots proving that what you’re saying is not correct:

    I’m not talking specifically about Plasma, I’m talking about the “DE” part of KDE in general; and particularly in this context of repurposing and extending the life of old PCs.

    I find it a bit ironic for KDE to be pushing this message, when it’s a heavy DE (relatively speaking) - it’s NOT what anyone would have in mind when when selecting a DE for an old PC.

    For instance, take LXQt - run the default/recommended file browser, terminal and text editor, and compare it with KDE + equivalents - you’d see a significant difference in resource consumption. On a system with low RAM, that extra bit of free memory makes a big difference, as it could mean avoiding the penalty hit of the swap file, which you’d invariably run into as soon as you fire up a modern Web browser. So it’s vital that the DE use as little resources as possible on such a machine.



  • Sounds like an issue with your WiFi adapter/driver. You can verify this by creating a mobile hotspot on your phone and connecting your PC to it and see if you get the same issue, if you do then it proves it’s got nothing to do with your router.

    Another thing you can check is your journalctl logs - run journalctl -f before launching the game, then run the game and quit it when you run into the DNS issue, and check the logs at the time the issue occurred. If there’s indeed a hardware/driver issue, the errors should show up in the logs.

    If it’s a driver issue, there may not be much you can do about it besides reporting the bug and implementing some sort of workaround (eg using a VPN). Of course, depending on the error, there may be a fix you can apply, like turning of aspm for your chip. A better option would be to replace the WiFi chip/adapter you’re using and get something that’s better supported under Linux, like something with an Intel or Atheros chip. But check journalctl first and see how it goes from there.



  • Bazzite. Here’s why:

    • Optimised for gaming (gaming optimised kernel, common tweaks pre-applied, all common gaming apps pre-installed like Steam, Mangohud etc)
    • All necessary drivers pre-installed (game controllers, RGB, and even proprietary nVidia)
    • A Steam-Deck like gaming experience, if you want (the Deck variant boots directly to Steam)
    • Immutable and atomic (image-based OS updates, so updates either work or don’t - there’s no chance of a broken state)
    • Easy rollbacks (just select the previous image in the GRUB menu)

    But since you said:

    how to squeeze the best performance out of this

    and if you’re really serious about squeezing the best performance, then check out the Arch-based CachyOS - unlike most other Linux distros, Cachy has optimised x86-64-v3 and v4 packages in their repos, which means apps can make use of advanced CPU instructions such as SSE3, AVX512 etc. Most other Linux distros on the other hand still use x86-64-v1 for compatibility reasons, which unfortunately means that you’d be missing out on all the cool new optimised CPU instructions introduced over the past 16 years.

    You can read more about microarchitecture levels (aka MARCH) here: https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels

    In addition to the MARCH, Cachy’s packages have other optimisations such as LTO/PGO, optimised kernel with the BORE and Rusty schedulers which are better for gaming, plus several performance-oriented tweaks which you’d otherwise have to do manually on Arch (such as makepkg.conf tweaks, pacman.conf tweaks etc).

    Finally, Cachy are always on the bleeding edge when it comes to gaming/driver/kernel/performance related stuff, so you’ll get all the good stuff even before Bazzite or other optimised distros. For instance, Cachy was the first distro to include the new nVidia driver which has explicit sync support for better Wayland compatibility, and they’re always on top of major Arch developments and provide detailed announcements which are relevant to gamers and performance freaks.

    Eg, here’s their recent recent nVidia announcement:

    Hi @here,

    as you maybe noticed, we have rolled out the new NVIDIA Driver, which includes the explicit sync protocol and tearing for Vulkan. We have been prioritized to move this forward to finally resolve the wayland situation. Additionally arch has pushed CUDA to 12.5, which is NOT compatible with the current 550 driver (it needs the 555 Driver).

    The beta driver is not perfect, but so far we are applying some fixes to avoid issues and restore performance problems with disabling the GSP Firmware load. This is handled via the “cachyos-settings” package.

    Anyways, since some people maybe have problems with this driver, here is a short instruction to manually downgrade and block the driver:

    […]

    If you are facing issues with the new NVIDIA Driver, reproduce the issues and then run “sudo nvidia-bugreport.sh” and report it to their forum: https://forums.developer.nvidia.com/c/gpu-graphics/linux/148

    We are also shipping now an precompiled nvidia-open module. This will be also as default installed for users, which have supported cards as soon NVIDIA releases the 560 drivers.

    The CachyOS Team

    So as you can see, they’re pretty on to it with this sorta stuff.

    Now the Bazzite team are also like the Cachy guys and keep up with this stuff, but because they’re based on Fedora, they can’t be as bleeding edge or as optimised as Arch. So it’s up to you - if you prefer stability, a primarily gaming-focused optimisations, and want something that “just works” then get Bazzite; or if you want an ultra-optimised distro to squeeze out the most performance out of your box but also don’t mind ocassionally diving into the terminal and getting your hands dirty, then get CachyOS.

    cc: @01189998819991197253@infosec.pub




  • You cannot go back after trying it

    I did! Used to have a Samsung 49" ultrawide. After using it for a couple of years, I sold it and got a 16:10 32" QHD, which I found worked better for me (+ one or two laptop screens for chat / random stuff when I’m doing serious work).

    The biggest issue I had with the ultrawide is that most of the games that I played weren’t optimised for it, especially in some games where things like the mini-map might be at the far end of the screen, or worse, if it was an older game then you’d have to put up with black bars, or play the game in windowed mode.





  • I’m not sure who this Chris Titus is, but I can’t believe there’s no mention of Bazzite in that infographic, which is surprising because it’s arguably the best distro for gaming right now (and a pretty decent newbie-friendly distro too). It’s also surprising there’s no mention of CachyOS, which is overall the best performing easy-to-install Linux distro right now (although since it’s based on Arch, I wouldn’t recommend it for newbies).

    So if I were you, I wouldn’t put too much faith in their video when they missed out on these two (and several other cool distros such as Bluefin, SecureBlue, AntiX etc).

    In saying that, nVidia on Linux sucks in general, so I second @ulkesk@beehaw.org’s suggestion and recommend getting an AMD instead - it’s so much more nicer and hassle-free, not having to deal with any proprietary driver bs, and having a smooth Wayland experience.