1. Forum
  2. Usenet
  3. COMP.SYS.MAC.SYSTEM

  • M3 memory utilization

    From Alan Browne@21:1/5 to All on Mon Dec 11 09:39:38 2023
    On my i7 iMac, with 24 GB of memory, it seemed happy to settle around 10
    - 12 GB of memory in use at any given time for whatever my "usual" load
    of apps was. The apps I use in daily grind are rarely shut down.
    When using more hungry apps, of course that would grow - but they would
    be shut down usually the same day.

    I wanted to get more memory with this M3 iMac ... up to 48 GB to have
    breathing room and some future proofness margin. Alas, at the end of my
    rope waiting wise, it was offered with 24GB max.

    Given the Mx memory "unification" I expected there to be less memory utilization with the same typical loaded apps for my workday.

    But ... it seems to have settled at around the same levels as on the
    prior iMac, indeed, typically 14 .. 15 GB are in use. The OS is leaving
    more of itself "loaded" at any given time. Kudos speedwise I guess.

    Chrome on Mx seems to forget to deallocate memory. Every few days I
    have to blow it off to recover a couple GB of memory. I assume that
    good languages and programs these days request memory from the OS and
    that it can be returned to the OS. Chrome devs don't seem to have
    gotten the memo.

    Regrettably, Chrome is still my go to for many things, but I use Safari
    more and more, esp. as I use the Password feature of the Mac more. Just
    wish Chrome had access to it.

    --
    “Markets can remain irrational longer than your can remain solvent.”
    - John Maynard Keynes.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan Browne@21:1/5 to gtr on Mon Dec 11 13:36:42 2023
    On 2023-12-11 13:26, gtr wrote:
    On Dec 11, 2023 at 6:39:38 AM PST, "Alan Browne" <[email protected]> wrote:

    Chrome on Mx seems to forget to deallocate memory. Every few days I
    have to blow it off to recover a couple GB of memory. I assume that
    good languages and programs these days request memory from the OS and
    that it can be returned to the OS. Chrome devs don't seem to have
    gotten the memo.


    How to you perform this "blow off" to recover memory?

    Really? Quit the program. The OS recovers all memory allocated to it.

    --
    “Markets can remain irrational longer than your can remain solvent.”
    - John Maynard Keynes.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From gtr@21:1/5 to All on Mon Dec 11 18:26:24 2023
    On Dec 11, 2023 at 6:39:38 AM PST, "Alan Browne" <[email protected]> wrote:


    On my i7 iMac, with 24 GB of memory, it seemed happy to settle around 10
    - 12 GB of memory in use at any given time for whatever my "usual" load
    of apps was. The apps I use in daily grind are rarely shut down.
    When using more hungry apps, of course that would grow - but they would
    be shut down usually the same day.

    I wanted to get more memory with this M3 iMac ... up to 48 GB to have breathing room and some future proofness margin. Alas, at the end of my
    rope waiting wise, it was offered with 24GB max.

    Given the Mx memory "unification" I expected there to be less memory utilization with the same typical loaded apps for my workday.

    But ... it seems to have settled at around the same levels as on the
    prior iMac, indeed, typically 14 .. 15 GB are in use. The OS is leaving
    more of itself "loaded" at any given time. Kudos speedwise I guess.

    Chrome on Mx seems to forget to deallocate memory. Every few days I
    have to blow it off to recover a couple GB of memory. I assume that
    good languages and programs these days request memory from the OS and
    that it can be returned to the OS. Chrome devs don't seem to have
    gotten the memo.


    How to you perform this "blow off" to recover memory?

    Regrettably, Chrome is still my go to for many things, but I use Safari
    more and more, esp. as I use the Password feature of the Mac more. Just
    wish Chrome had access to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From gtr@21:1/5 to All on Tue Dec 12 07:10:12 2023
    On Dec 11, 2023 at 10:36:42 AM PST, "Alan Browne" <[email protected]> wrote:

    On 2023-12-11 13:26, gtr wrote:
    On Dec 11, 2023 at 6:39:38 AM PST, "Alan Browne" <[email protected]> >> wrote:

    Chrome on Mx seems to forget to deallocate memory. Every few days I
    have to blow it off to recover a couple GB of memory. I assume that
    good languages and programs these days request memory from the OS and
    that it can be returned to the OS. Chrome devs don't seem to have
    gotten the memo.


    How do you perform this "blow off" to recover memory?

    Really? Quit the program. The OS recovers all memory allocated to it.

    Ah! I call that quitting the program. I've never heard it called a blow off.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan Browne@21:1/5 to gtr on Tue Dec 12 09:21:07 2023
    On 2023-12-12 02:10, gtr wrote:
    On Dec 11, 2023 at 10:36:42 AM PST, "Alan Browne" <[email protected]> wrote:

    On 2023-12-11 13:26, gtr wrote:
    On Dec 11, 2023 at 6:39:38 AM PST, "Alan Browne" <[email protected]> >>> wrote:

    Chrome on Mx seems to forget to deallocate memory. Every few days I
    have to blow it off to recover a couple GB of memory. I assume that
    good languages and programs these days request memory from the OS and
    that it can be returned to the OS. Chrome devs don't seem to have
    gotten the memo.


    How do you perform this "blow off" to recover memory?

    Really? Quit the program. The OS recovers all memory allocated to it.

    Ah! I call that quitting the program. I've never heard it called a blow off.

    Apologies, thought it was obvious.

    --
    “Markets can remain irrational longer than your can remain solvent.”
    - John Maynard Keynes.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)