this post was submitted on 02 Dec 2025
208 points (98.6% liked)

Technology

77084 readers
2625 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] unhrpetby@sh.itjust.works 2 points 2 days ago (1 children)

High memory usage isn't a problem by itself.

The issue is when it's used inefficiently or for useless purposes. An unoptimized application takes 500MB of extra memory and that is 500MB that cannot be used for read/write caching nor another application, and 500MB closer to an OOM situation.

In theory, an application can suffer from issues of underutilization of memory, just as one that over-utilizes memory. In practice, I find that lower-than-expected memory use is a much more positive indicator of an optimization-focused project than one that uses more memory than expected.

In the meantime, it's not sitting there, unused and useless.

If your system uses caching, then "usused" memory may not be so. Memory used for caching is also cleanly "Available" for use if needed. This is not the case with the 500MB of extra memory a process might decide to capture. Of course this is complicated further with swap (I wouldn't use it).

[โ€“] ragepaw@lemmy.ca 2 points 2 days ago

This is my point.