• Midnight Wolf@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    28 days ago

    Ehh, my main machine eats up 12-16GB with just background tasks, and that’s on W10. Nobody gives a fuck about optimization since the late 00s.

    • zarathustrad@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      28 days ago

      Well, I’m installing Linux (CachyOS) on my former W10 PC this weekend. So, my 16gb of ram will be well utilized.

      At least someone still cares about optimization.

      • taiyang@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        28 days ago

        And CachyOS running KDE Plasma is the most RAM hungry setup. I took a Win 11 laptop with 8gb and threw Debian running Xfce and that’s using like 300mb of RAM lol

        • zarathustrad@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          28 days ago

          I guess going from 7-8 to 600-1.2k seemed like such an improvement I didn’t think to GO HARDER to 300. Though my Ubuntu server VMs get that I assume lol.

    • Brkdncr@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      28 days ago

      Ram usage isn’t important, it’s how much your page being hit. Otherwise you want your ram fully utilized.

      • halcyoncmdr@piefed.social
        link
        fedilink
        English
        arrow-up
        0
        ·
        27 days ago

        The number of people that still don’t understand this, even after it’s been discussed ad nauseum for decades is frightening.

        Unused RAM is wasted RAM. You want it used. You want cached data there for instant access. What matters is how much is available for something else if you need it, and Windows does a shit job of getting that info across.

      • Midnight Wolf@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        27 days ago

        I’m pretty sure I have the pagefile disabled; both C and D are NVMe drives, and D is raid0. I disabled superfetch a few minutes ago, rebooted, and don’t see any performance impact, but the used memory when idle is now 10GB, vs the 19 in that screenshot. No other changes.

        I could see the appeal if I was using a platter drive for my programs or frequent data, but it’s not 2008 anymore. I’d rather see actual usage over ‘the computer knows best’.

        E: me spell good

      • Midnight Wolf@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        27 days ago

        I haven’t heard of that since the Vista days, totally forgot about it. Doesn’t make sense, I’ve been all-flash* (E is still HDD for backups, no programs) for well-over a decade. Maybe I should disable it and see if it makes a difference. C is a Samsung 960 Pro and D is a Western Digital Black SN750 in raid0, so it’s not really helping even if it is doing something…

        • Romkslrqusz@lemmy.zip
          link
          fedilink
          English
          arrow-up
          0
          ·
          27 days ago

          The alternative is your CPU spooling up and a longer delay launching applications.

          In your screenshot, you already have 70% available memory. Are you on a quest to maximize idle ram? If so, why?

    • Jean-luc Peak-hard@piefed.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      27 days ago

      My Linux system (which used to run Window so it has 32 GB of RAM), won’t even hit 8 GB if I’m not gaming. I’ve opened up multiple apps just to show how efficient it is. I think it was sitting around 4 GB before I started running things to see if I can make it balloon easily.

      HB4EGPTi4hgvwHb.png

      And I’m running most my apps as flatpaks which I’ve heard may add some slight overhead in terms of RAM usage - someone correct me if I’m wrong about this.

      My work computer (granted it likely has tons of background security tools running) uses 10/16 GB’s just to get to the desktop and do nothing. The best part is, because ~1.2 GB’s of RAM gets allocated for the integrated graphics, I’m really only left with ~4.8 GB’s of RAM to do actual work. But wait, it gets even better! This week I found out some bullshit Copilot feature was enabled and taking up another ~1.2 GB’s of RAM, leaving me with a total of 3.6 GB’s of RAM. So I disabled the WSAIFabricSvc service and reclaimed a sliver of dignity and work space.