SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't know why some of you get such high RAM usage even with Akonadai running. My Main has 3 hard drives divided into 22 partitions including FAT, FAT32, NTFS, HPFS, EXT3, and EXT4 (a lot of polling) yet I commonly idle at 6% RAM (< 500MB) even running an extensive Conky to monitor that usage and with all of the Akonadai, Baloo, etc "offenders" in place. If you need proof or are merely interested, I'll link a screenie and please notice that of the top 4 "memory hogs", Krunner is included (I love that feature) but Python is right up there at 4th.
I don't know why some of you get such high RAM usage even with Akonadai running. My Main has 3 hard drives divided into 22 partitions including FAT, FAT32, NTFS, HPFS, EXT3, and EXT4 (a lot of polling) yet I commonly idle at 6% RAM (< 500MB) even running an extensive Conky to monitor that usage and with all of the Akonadai, Baloo, etc "offenders" in place. If you need proof or are merely interested, I'll link a screenie and please notice that of the top 4 "memory hogs", Krunner is included (I love that feature) but Python is right up there at 4th.
I am legit curious, I do not know what I need to do differently as initially it is all a full install, and this is all in a VM too; but as far as I can remember even in KDE3 , I do recall seeing a lot of Akonadi processes and significant amount of RAM usage, that was on an older system though; so yea I honestly do not know why or how for you it is not the case and for others like me it is.
When I have more time, I will do a new full installation of --Current and leave Akonadi and KDE-PIM packages installed as well and I will check again the processes and RAM usage now, as I am curious even more.
Distribution: KDE Neon, Mageia, Kubuntu, openSUSE, PCLinuxOS, Mint KDE, Slackware, Arch, Sabayon, Debian, Devuan
Posts: 41
Rep:
Quote:
Originally Posted by enorbet
I don't know why some of you get such high RAM usage even with Akonadai running. My Main has 3 hard drives divided into 22 partitions including FAT, FAT32, NTFS, HPFS, EXT3, and EXT4 (a lot of polling) yet I commonly idle at 6% RAM (< 500MB) even running an extensive Conky to monitor that usage and with all of the Akonadai, Baloo, etc "offenders" in place. If you need proof or are merely interested, I'll link a screenie and please notice that of the top 4 "memory hogs", Krunner is included (I love that feature) but Python is right up there at 4th.
There is a difference between "PIM suite installed" and "Akonadi running".
All PIM suite has been reinstalled here, after a complete upgrade of openSUSE Tumbleweed ─ and it didn't change my RAM usage, about 500 MiB at startup, with Weather and Moon phase widgets, and also BtrFS / Snapper services.
No Akonadi process running, by now.
Just start some PIM app ─ such as KMail, or Kontact ─ and all 17 Akonadi processes + 1 SQL process will start.
After this, they will automaticly run in every new session, and RAM usage will be bigger at startup.
So, you may not remove PIM suite, since you take care not to run any PIM app. ─ I prefer just to remove all PIM suite.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Quote:
Originally Posted by enorbet
I don't know why some of you get such high RAM usage even with Akonadai running. My Main has 3 hard drives divided into 22 partitions including FAT, FAT32, NTFS, HPFS, EXT3, and EXT4 (a lot of polling) yet I commonly idle at 6% RAM (< 500MB) even running an extensive Conky to monitor that usage and with all of the Akonadai, Baloo, etc "offenders" in place. If you need proof or are merely interested, I'll link a screenie and please notice that of the top 4 "memory hogs", Krunner is included (I love that feature) but Python is right up there at 4th.
shrug,
it really depends how one is running OS, no necessary KDE/Plasma5.
How DE/WM is loaded (e.g. I use sddm but memory will be saved if you start DE manually), wallpaper size (slideshow or single pic?) additional services that run and so on.
I doubt that 100MB one way or another really matter.
akonadi will not start unless invoked, same with baloo (needed for dolphin by the way), same thing with krunner
Lots of modern programs would've been considered spyware 20 years ago. If someone told me then about the rent-an-OS-win10 back then, I'd probably laugh.
The cloud sync function is considered a benefit now, because big companies decide so. Viruses used to sync to remote servers way before it was called cloud.
Social media applications apparently connect lots of devices together in a closed group, which used to be called a botnet.
Even the modern filesystems could be seen as spyware by the old standards, because of the MFT, journals, etc.
Packages like snaps and similar? They used to be called trojans, when one program exploded into 20 more programs bundled inside it.
Akonadi has source available, so I don't think it's real spyware. Probably just some dev reaching out a bit too far outside his scope.
It can happen to any project at any time, which is why input/output firewall filter is very important these days.
There is a difference between "PIM suite installed" and "Akonadi running".
All PIM suite has been reinstalled here, after a complete upgrade of openSUSE Tumbleweed ─ and it didn't change my RAM usage, about 500 MiB at startup, with Weather and Moon phase widgets, and also BtrFS / Snapper services.
No Akonadi process running, by now.
Just start some PIM app ─ such as KMail, or Kontact ─ and all 17 Akonadi processes + 1 SQL process will start.
After this, they will automaticly run in every new session, and RAM usage will be bigger at startup.
So, you may not remove PIM suite, since you take care not to run any PIM app. ─ I prefer just to remove all PIM suite.
Of course I understand that difference but I've made another screenie to show as many of the 200+ running processes this afternoon as will fit on my screen. As you can see, there are several instances of Akonadi running and while my RAM usage is up over 100MB from the previous screenie, 4 new widgets and KSysguard itself are responsible for most of that. I think you will agree that very few PIM services are near the top of the list and usage is still well under 10%... CPU @ 1%
Distribution: KDE Neon, Mageia, Kubuntu, openSUSE, PCLinuxOS, Mint KDE, Slackware, Arch, Sabayon, Debian, Devuan
Posts: 41
Rep:
Quote:
Originally Posted by enorbet
Of course I understand that difference but I've made another screenie to show as many of the 200+ running processes this afternoon as will fit on my screen. As you can see, there are several instances of Akonadi running and while my RAM usage is up over 100MB from the previous screenie, 4 new widgets and KSysguard itself are responsible for most of that. I think you will agree that very few PIM services are near the top of the list and usage is still well under 10%... CPU @ 1%
Ok, so your previous screenie https://i.imgur.com/sbxEoEe.png with 483 MiB of RAM usage included Akonadi processes ─ it is a very nice low usage, for running PIM and for 1 hour uptime.
Are you using KDE4 ?
In all cases, I was using KDE5. ─ When I said the RAM usage at startup did fall from 800 to 400 MiB (and later even to 365 MiB), it was a specific Kubuntu 16.04 case, back in 2016. ─ I have seen many different RAM usage cases, from one distro to another.
Also, I didn't try to consider "Memory" or "SharedMem" from individual processes in KSysguard. ─ Instead, I always consider the whole RAM usage circa 1 minute after KDE session is loaded.
Until December 2018, with only Conky ─ and Slackware by AlienBOB (KDE5) used circa 374 MiB.
Since April 2019, also with Weather + Moon Phase widgets, which use circa 55 MiB more. ─ So, Slackware by AlienBOB (KDE5) used circa 427 MiB.
Here recent averages, from December 2019 ─ all distros with KDE5:
Code:
RAM usage at startup (*)
385 MiB Void LXQt + KDE
389 MiB Void “minimal” + KDE
412 MiB KDE Neon
427 MiB Slackware by AlienBOB
429 Mib Arch KDE
436 MiB Arch KDE (by Revenge)
446 MiB Sabayon KDE
467 MiB PCLinuxOS KDE
489 MiB Mageia KDE
493 MiB openSUSE KDE
522 MiB Debian testing KDE
565 MiB Fedora KDE
(*) with circa 55 MiB from Weather + Moon widgets
In all cases, without PIM and Baloo (disabled File Search), and without automatic "check updates". ─ openSUSE RAM usage including BtrFS + Snapper services. ─ Mageia including MSEC service. ─ I don't know why Debian was using so much RAM.
Yes. On 14.2 I'm using KDE 4. I have Plasma 5 on a separate -Current install and that is very well-behaved. One of the great things about Slackware Full Install is that it is so easy to drop to Fluxbox if I'm planning on spending most of a day in DAW. For gaming, I don't even bother. I just stay in KDE. Any difference in performance is insignificant.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
I've never liked akonadi either, since it really doesn't show us what it's actually *doing*. I probably can't disable it though since I pretty much depend on kalarm and love the heck out of klipper...as far as I know, there's nothing outside KDE stuff that does either of those two jobs. It also looks like browsers depend on akonadi, at least according to the screenshot here I'm posting up. I put 'akonadi' as the only process to look for and I got that mysql thing and SeaMonkey. I opened up Firefox and checked it and it didn't show up on ksysguard, nor did Opera Developer, only the SeaMonkey, as a browser, seems to need akonadi.
I'll experiment a little and set akonadi to not start up at start of my system and see what stops working.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Rep:
A day or two ago I installed the latest "pam ready" kde5 into -current ("pamified" ), but did not install anything from the the pim directory, which includes akonadi.
SeaMonkey runs just fine without akonadi and I'm typing this message in SeaMonkey "as we speak."
Just FYI.
Last edited by cwizardone; 02-15-2020 at 08:35 AM.
I've never liked akonadi either, since it really doesn't show us what it's actually *doing*. I probably can't disable it though since I pretty much depend on kalarm and love the heck out of klipper...as far as I know, there's nothing outside KDE stuff that does either of those two jobs. It also looks like browsers depend on akonadi, at least according to the screenshot here I'm posting up. I put 'akonadi' as the only process to look for and I got that mysql thing and SeaMonkey. I opened up Firefox and checked it and it didn't show up on ksysguard, nor did Opera Developer, only the SeaMonkey, as a browser, seems to need akonadi.
I'll experiment a little and set akonadi to not start up at start of my system and see what stops working.
SeaMonkey is listed because the window title contains akonadi.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Ah, okay, good to know about the SeaMonkey.
As for turning off all things akonadi, it did stop kalarm from working. As soon as I clicked on it on the panel it popped up with a little notice saying it can't work without akonadi and provided a little 'start' button to click and all those akonadi things and the mysql thing were right back up and running wasting memory. It's not a lot on my system as I have 12GB of RAM, but still, all those akonadi's running just for kalarm at the very least. Meh, oh well, life in the woods I guess.
So I did a full install of latest --Current and left Akonadi and KDE-PIM packages - this is the memory usage at launch of KDE4 and process list:
Launching KMAIL now and it is at 710MB:
The number of Akonadi processes actually stayed the same - and yes it was 15 process under sql and I do not see the point why that is, and if I can shave 300MB off, why not? I am still curious about KDE5 when it hits Slackware , if it is not as significant to just keep Akonadi and PIM, or if I can shave off more if I remove these packages. On the one hand yes we are not in the days where RAM was an issue, but to me on the other hand still - why does it still need even that much RAM (few hundred MB) to begin with? I don't really need what PIM offers me anyways, so again whenever I do decide to plunge back into KDE and Slackware goes to KDE5 LTS hopefully - I most likely still will be removing Akonadi and PIM packages.
So yea, I still stand by statement - screw Akonadi - remove it along with KDE-PIM.
Akonadi is licensed LGPLv2.1! Software licensed with GPL, generally won't contain spyware, as that is the entire point of the GPL licensing. Its developers share its source code, so you can audit it and make sure its not spyware if you feel like it. IMHO spyware is more likely lurking in executable binary code for which no source code was shared--and there are plenty of these blobs in slackware, such as Broadcom's bluez-firmware (what... could my bluetooth headphones be spying on me?) and all these other blobs on slackware.
If you are worried about spyware, perhaps you should try freenix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.