Comment on RAM prices soar, but popular Windows 11 apps are using more RAM due to Electron, Web components

_cryptagion@anarchist.nexus ⁨4⁩ ⁨weeks⁩ ago

• cmnybo@discuss.tchncs.de ⁨4⁩ ⁨weeks⁩ ago

  Yes, it runs a separate browser instance for each electron program. Many of the programs that use it could just be a PWA instead.

  source

  • lastweakness@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

    This is what bothers me so much… Browsers should be improving their PWA implementation (looking at you, Firefox) and electron apps should be PWAs more often. Another decent middle ground Is Tauri. SilverBullet and Yaak are both so much lighter and better than anything else on my system.

    source

    • Pechente@feddit.org ⁨4⁩ ⁨weeks⁩ ago

      Yeah but companies want full control and no ad blockers. That’s why they’re pushing shoddy Electron apps over their mobile experiences and PWAs.

      source
  • tal@lemmy.today ⁨4⁩ ⁨weeks⁩ ago

    I wonder how much exact duplication each process has?

    www.kernel.org/doc/html/latest/…/ksm.html

    Kernel Samepage Merging

    KSM is a memory-saving de-duplication feature, enabled by CONFIG_KSM=y, added to the Linux kernel in 2.6.32. See mm/ksm.c for its implementation, and lwn.net/Articles/306704/ and lwn.net/Articles/330589/

    KSM was originally developed for use with KVM (where it was known as Kernel Shared Memory), to fit more virtual machines into physical memory, by sharing the data common between them. But it can be useful to any application which generates many instances of the same data.

    The KSM daemon ksmd periodically scans those areas of user memory which have been registered with it, looking for pages of identical content which can be replaced by a single write-protected page (which is automatically copied if a process later wants to update its content). The amount of pages that KSM daemon scans in a single pass and the time between the passes are configured using sysfs interface

    KSM only operates on those areas of address space which an application has advised to be likely candidates for merging, by using the madvise(2) system call:

    int madvise(addr, length, MADV_MERGEABLE)

    source

    • fuckwit_mcbumcrumble@lemmy.dbzer0.com ⁨4⁩ ⁨weeks⁩ ago

      I guess the key is it has to be the same version of electron in the back end. If they change too much of it then how much memory can be shared?

      source
  • plz1@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

    I tried the PWA route with Discord. It wouldn’t stay logged in, and acted generally janky. That said, I do PWA with any app that’s Electron, at least to try and avoid the RAM bloat.

    source
  • SaraTonin@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Or, even better, let’s start developing for separate platforms again, and optimise software for the platform that’s going to be running it. Rather than just developing everything for Chrome.

    source
• modular950@lemmy.zip ⁨4⁩ ⁨weeks⁩ ago

  maybe a toggle to choose between “take some extra RAM, I’m feeling generous” and “fuck you, I’m computing shit over here” could be used to let the app know your current mood / needs …

  source

  • TheBlackLounge@lemmy.zip ⁨4⁩ ⁨weeks⁩ ago

    Memory hogging browsers usually do release memory when pressured. You can take it further by getting extensions that unload unused tabs.

    The problem electron apps that load the whole browser core over and over.

    source