• AVincentInSpace@pawb.social
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    3
    ·
    27 days ago

    Unused RAM is wasted RAM. It consumes the exact same amount of power whether there’s useful data in it or not. Any self-respecting operating system will fill up RAM that applications aren’t using with frequently accessed files, so they’re ready to go in an instant.

    • Draconic NEO@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      13
      ·
      edit-2
      26 days ago

      I think that’s precisely why limiting RAM on apps like Chrome or Firefox is so necessary, these apps never release their RAM when they are supposed to, they hoard anything that isn’t free and don’t give back when it’s needed, which is why in the reply to the top comment I shared a desktop entry to limit RAM on Firefox or whatever app you so choose.

      • AVincentInSpace@pawb.social
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        edit-2
        26 days ago

        Oh, I totally agree. Being afraid to call out to the allocator because “hey, I might need that memory later” is kinda not great. To a certain extent I can see how if an application tends to thrash memory, making a kajillion syscalls might hurt performance, enough that on many machines the gains from doing a single big allocation on the system and then slicing it up into small allocations in-process might outweigh the downsides, but still…