I've been using 1 for 1 for on my swap partitions for about 15 years now and not really had issues, but it probably is a good idea to switch to 2 for 1 as you suggest.
I don't use ANY Akondi apps. None, zero, zilch. The memory problems start at boot before I've even opened an application. Not sure what I would configure on Calendar. I was under the impression that if you open ANY Akondi enabled app it brings the whole Akondi system up. Why would I want to do that since I do not use any of the apps? Kmail is the only one I'd be tempted to use and only to read archived mail on rare occasion.
Yes Chrome can eat some RAM. Though the cost per tab is pretty small with Chrome and is quickly recovered when the tab is closed. One of my gripes with FF is that you don't recover the memory from a tab until you close the window that held the tab from what I can tell. I tend to keep my add ons down to a minimum.
Actually it's not a problem with Akondi disabled. It's a little slow on only 2 gigs. On 4 gigs I suspect it will be fine. With KDE 4 I do it every day all day on only 4 gigs of RAM. Linux is a superb multi-tasker and usually handles memory very gracefully.
On Sun, Sep 2, 2018 at 4:00 AM René J.V. Bertin <rjvbertin@xxxxxxxxx> wrote:
On Saturday September 01 2018 21:51:57 Draciron Smith wrote:
>
>On the first machine machine I put KDE 5 on, it only has 2 gigs of ram and
>2 gig swap partition. It's sort of reflex for me to create swap partition
>same size as ram. In hindsight I probably should have gone with a 4 gig
The reflex should be to create a swap partition 2x the size of RAM. More is possible but I'm not sure if it will help.
Of course one uses a fast part of the disk for this ;)
Running the kind of session you describe on a machine with only 2Gb of RAM is probably an exercise in SM with any modern DE... Chrome readily uses around 600Mb just for the central process, FireFox even more; extensions like AdBlock run as a separate process and can grow quite large; the same applies for each tab you open. Audacity is surprisingly lightweight in comparison, even for large projects.
(You'd at least need to install The Great Suspender in all the browsers you use.)
>That's the thing. I am not using ANY Akondi agents. I use webmail clients
>for email, my phone is my contact manager, I never use Knotes or any other
>Akondi enabled apps.
So what akonadi process was hogging?
I don't think I ever had zero akonadi agents configured, did you ever try to add a single agent that's unlikely to use a lot of resources, like a local calendar? There is (or used to be) an akonadi dependency in the default clock panel widget, and I could imagine that no one thought to check how that behaves when akonadi is running without any agents. The akonadi server is the central access hub for all PIM functionality and badly written clients could well bombard it with requests if they detect akonadi on the dbus without ever checking if the agent they want is available.
R.
