I'm not saying there's no such thing as software bloat (there is) but the reason that your computer magically always seems to use 80-90% of the ram no matter how much ram you install is that the computer understands empty ram doesn't do anything but ram being used to cache files makes your user experience much faster
this is a good thing! if your computer stopped doing this everything would suddenly feel very sluggish and stuttery!
Gidi Kroon likes this.
Rich Felker
in reply to abadidea • • •eater
in reply to Rich Felker • • •Max
in reply to eater • • •@eater @dalias @chucker We have the worst of both worlds already. We *have* chrome (or safari) near the kernel in every major OS and then electron comes along and suggests the OS chrome isn’t enough and we need to stack more chromes like turtles in userspace because you all love chrome so much
“Yo dawg, I heard you like chrome so I boooted more chrome from your chrome so you can chrome while you chrome.”
abadidea
in reply to Max • • •@max sorry for the late reply but I am very confused. You appear to be describing an architecture where the main chrome installation is on a special ultra low layer of existence near the metal, and then additional copies of chrome in electron are not, and it sounds like you think electron is chrome implemented on top of chrome?
I am not aware of any system that works that way. Main chrome and electron chrome are two copies of the same app running on the same level of user space, the only difference is that one is configured to run a single web app in isolation
Max
in reply to abadidea • • •I took some liberties for amusement, it’s not exactly “technically correct” in all cases, but some of the OS level app launchers are web views (or related/derived tech) and it is funny using them to launch electron apps.
The boundaries between “kernel” and “userspace” are fuzzy in the graphical side of the modern OS, especially today when even core functionality is shipped as “apps” for software lifecycle reasons, and the main browser has some light privileges others don’t.
abadidea
in reply to Rich Felker • • •Shorty
in reply to abadidea • • •Jos :donor:
in reply to abadidea • • •abadidea
in reply to abadidea • • •ĸurth
in reply to abadidea • • •on #linux, with
% echo 3 > /proc/sys/vm/drop_caches
as root one can experience this hands on
Distro's Projects
in reply to abadidea • • •Fritz Adalis
in reply to abadidea • • •If you're not running at 100% cpu, ram, and I/O all the time then you wasted your money.
Echo 🦊
in reply to abadidea • • •abadidea
in reply to Echo 🦊 • • •Yossi
in reply to abadidea • • •JamesGecko
in reply to abadidea • • •PlasmaGryphon
in reply to abadidea • • •my issue is that it seems to fail frequently in ways that noticable affect system performance. I've always assumed it was trying to cache things...but something is off about the priority. When the computer reboots and loads all of my major programs in under a minute, how much more caching do I really need?
On windows systems with 48-64GB of ram I had to reboot once or twice a week because I've had it bog down and appear to use a page file on hard drive (which I wish it never did on SSD). RAM will 90%+ used, but if I tally up individual programs it will be closer to 25%. I assume this is primarily OS then, although individual programs could be aggravating the caching system.
Linux has been smoother and less frequent problems...but I still catch browser suddenly asking for 32+GB of ram and suddenly stuff like X and bash crash from out of memory issues while browser keeps allocating. (I realize this is what I would get if I force no page file...).
SpaceLifeForm
in reply to abadidea • • •Ivain
in reply to abadidea • • •Chickerino
in reply to abadidea • • •