Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overall: how to reduce memory footprint #21

Open
star-buck opened this issue Jan 16, 2019 · 13 comments
Open

Overall: how to reduce memory footprint #21

star-buck opened this issue Jan 16, 2019 · 13 comments
Assignees

Comments

@star-buck
Copy link
Contributor

star-buck commented Jan 16, 2019

Please download latest ISO and post ideas here.

@star-buck
Copy link
Contributor Author

star-buck commented Jan 16, 2019

This is memory after fresh start of 16.09:
screenshot_20190116_232811

Compare to 19.01:
approx 550 MB (screenshot will follow)

@llelectronics
Copy link

llelectronics commented Jan 17, 2019

This thread is about core release and not the desktop release. The core release uses breeze for window decoration and widget theme.
You can get the newest from here: http://ds9-eu.s3-website.eu-central-1.amazonaws.com/#!/dci%2Fimages%2F1901%2Famd64%2Fnetrunner-core%2F

@blue-systems blue-systems deleted a comment from davidedmundson Jan 17, 2019
@blue-systems blue-systems deleted a comment from davidedmundson Jan 17, 2019
@llelectronics
Copy link

Here a screenshot from a freshly booted Core 19.01
image

As you can see here plasmashell is eating more RAM for some reason. We did not change much in the overall setup like widgets aren't there. Just a panel with one icon more and folderview desktop

@zgrimshell
Copy link

Is this freshly booted on machine or VM? Also not sure for live session, but Xorg shouldn't be root nowdays anymore. That said - I personally don't think yakuake should be in default installations (not something I would at all recommend to average Joe and it is just another terminal so overhead if we have Konsole already. What is websockify? Not sure why plasma got fatter but this overall is not terrible (we do want to optimize as much as possible due to our project future needs but overall it is not horrible).

@llelectronics
Copy link

This is booted in a VM.
Yakuake is what we ship by default since ages. Its part of our branding that we ship this by default and have a panelicon to click to open it.
websockify is the daemon for accessing Netrunner Core via NoVNC from the browser.

@notmart
Copy link

notmart commented Jan 17, 2019

i notice that if i put the default wallpaper instead of that one, it becomes around ~105 mb instead of ~113.. maybe there isn't a wallpaper of the proper size provided?

@notmart
Copy link

notmart commented Jan 17, 2019

using kickoff instead of dashboard becomes ~97 (not sure how much is possible to do further optimization in dashboard, the thing is that is bigger with bigger graphics, so is normal that will take up more than a small menu)

the win7 mixer also seems to take around 2mb more than the default one (but that is a small difference)

i don't see much more differences with stock..
using the default look and feel, layout and everything, gets to approx ~90mb, which is still way more than that ~74 (note also the screen resolution plays a big factor as it means bigger pixmaps, so images should be compared with the exact same resolution and dpi)

i wonder if there have been recent upstream changes in some plasmoid which made it significantly more complex

@llelectronics
Copy link

Newest image fresh after boot with simple menu instead of dash. I don't see much of a difference so far.
image

@star-buck
Copy link
Contributor Author

star-buck commented Jan 17, 2019 via email

@notmart
Copy link

notmart commented Jan 18, 2019

as comparison, on neon devedition unstable, i get pretty much the same memory on same screen resolution

@kbroulik
Copy link

Doesn't it initially preload everything and then as you start using it a bit more it learns what applets you use and as such memory consumption will drop after a few days?

@notmart
Copy link

notmart commented Jan 21, 2019

16.09 didn't have applets popups preloading yet.
disabling preloading completely (PLASMA_PRELOAD_POLICY=none) gives similar results (around ~80MB) tough reintroducing the lag the first time a popup is opened

with 16.09 (with a resolution of 1024x768, apparently is the max resolution supports in virtualbox here) starts at @87MB, once i open all the popups once, goes to ~107MB

with the latest iso of netrunner core with simplemenu, preloading and same 1024x768 resolution, i get 91 mb with plasma just loaded no interaction, 107 after opening every popup (exactly the same as 16.09)

with plasma started, no interaction and preload completely disabled, 77MB, afer opening all popups again 107

with a resolution of 1680x1050(i can get it on latest netrunner, not 16.04), just loaded without preloading is ~98, with preloading ~105, after opening all applets ~118

a thing i also see incides is that after the first startup, there are consistently few megabytes more than the second because of thwo things:
on first startup there is that extra javascript interpretation for the default layout
and there is also a ton more SVG interpreting, which gets then dumped in a disk cache
same as the caching of pre-parsed qml files.
with preloading and a resolution of 1680x1050 to me the difference is around from 112 MB the first start vs 107 the second
without preloading goes from 102 to 98

@star-buck
Copy link
Contributor Author

star-buck commented Jan 21, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants