i try to lower the system’s overall ram usage after boot, without sacrificing essential (to me) features like update notifications, for instance.
now, whenever an update is avaiable, discover (kde) seems to let you know via its icon in the taskbar (never used discover before).
does there exist a low footprint alternative, which will still inform you once after booting into the os, but which will not permanently run as a background task?
is it safe to remove discover, when i still have eos-udate-notifier installed, or are they bound together?
what is your approach and do you have other ram tweak tips for eos?
to optimize ram usage is always to know what you do…
in KDE you have to check if baloo is running in behind you can switch that off and any other indexers…
you can check autostart also if there some update icon of discover is enforce to autostart, you can disable that also… but eos-update-notifier is a low ram print so thats not the problem.
yes, the usual stuff is already disabled (like baloo, animations, some extra services). there is no special use case, i just want keep a low-ram-footprint in general.
conky + plank is in autostart, and ram usage on a freshly booted system is about 620mb, which is not so bad. my “identical” manjaro install took about 540mb, so perhaps there is still some free space for ideas
i removed discover from the system, thanks. so eos-update-notifier is still supposed to inform on updates nevertheless, right? that is basically what i am looking for, i guess.
i noticed that (sometimes) there is a packagekitd process with about 55mb running in the background, which i don’t seem to remember (from manjaro)?
indeed that was slighty offtopic (just as i stated), although many enabled services are also affecting ram usage in the end, so it is circular flow if you like.
now, to a certain degree that is of course true. on the other hand, there is heavyweight browsers making real use of avaiable ram, where doing something else besides browsing slowly turns into an adventure…
personally i very much favour a system with a modest exposure of ram (despite its hardware-specs) and try to stay with tools that keep up to this philosophy as well. to be wasteful with resources in general is something i try to avoid.