Every panel applet on #Cosmic takes about 33 MB of RAM each, resulting to Cosmic using 2.4 GB of RAM on a cold boot.
-
replied to Eugenia L last edited by
@eugenialoli It's still in alpha. Don't expect everything to be optimized just yet (but other than that yes, RAM usage should be looked into).
-
replied to Simon Justesen last edited by
@simonjust This is an excuse I'm afraid and not in line with software engineering. To reduce RAM in this case, you'd need to re-architect part of it, and that would result in major new bugs. These changes needed to be done BEFORE we entered these public releases.
-
replied to Eugenia L last edited by
@eugenialoli "Not in line with software engineering"? Show me a properly engineered system with no bugs. They only exist in books
People have been arguing about how to do software engineering right for years, and no one does it. Not even those that are paid billions to do it.
I don't think Cosmic was intended to run on older, low-end machines in the first place. I think the target is to have it running on System76 PCs (8GB RAM baseline) and the rest is just a bargain
-
H [email protected] shared this topic
-
replied to Simon Justesen last edited by
@simonjust Look at the other reply here, the link shows where it doesn't fit on 8 GB of ram if the user has too many fonts or icon packs installed. Yes, you read that correctly..
-
replied to Eugenia L last edited by
@eugenialoli The link is missing, but yes if that's the case, there's clearly something wrong.
-
replied to Eugenia L last edited by
@eugenialoli If you read the issue then you'd understand it's not an architectural issue. Just a matter of some libraries needing more optimization work. Again, there's a lot of areas that can be optimized, and we'll get to them before the release. So I'd advise against making blanket judgements today as if this is the way things are always going to be.
-
replied to Michael A. Murphy :system76: last edited by
@mmstick @eugenialoli This makes. As a developer myself, we often make it work first, and then streamline it to make it performant.. At least thats how I work.
-
replied to Mike :nixos: last edited by
@codemonkeymike @mmstick @eugenialoli Right ? Optmizing when you still don't have a full picture of how everything works and fits together is a waste of time unless you're REALLY familiar with the domain you're working on. Early optimization is a project killer.
-
replied to ojonnysilva last edited by
@ojonnysilva @mmstick @eugenialoli exactly. I mean of course make good early organizational decisions. But over optimizing early really puts the cart before the horse.
