Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #58520 > unrolled thread

10.9 - disabling memory compression

Back to article view | Back to comp.sys.mac.system

Contents

  10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 12:07 -0400
    Re: 10.9 - disabling memory compression billy@MIX.COM - 2014-04-13 17:57 +0000
      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 15:35 -0400
    Re: 10.9 - disabling memory compression Warren Oates <warren.oates@gmail.com> - 2014-04-13 14:50 -0400
      Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-13 21:18 +0200
        Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 15:55 -0400
      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 15:37 -0400
        Re: 10.9 - disabling memory compression Warren Oates <warren.oates@gmail.com> - 2014-04-13 15:51 -0400
      Re: 10.9 - disabling memory compression Leonard Blaisdell <leoblaisdell@sbcglobal.net> - 2014-04-13 19:35 -0700
        Re: 10.9 - disabling memory compression Your Name <YourName@YourISP.com> - 2014-04-14 16:34 +1200
          Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-14 16:30 -0400
            Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 10:53 +0200
              Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-20 09:27 -0400
        Re: 10.9 - disabling memory compression Warren Oates <warren.oates@gmail.com> - 2014-04-14 07:51 -0400
          Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:35 +0000
        Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-14 16:30 -0400
          Re: 10.9 - disabling memory compression JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-14 17:36 -0400
            Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-14 18:06 -0400
            Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 09:15 +0200
          Re: 10.9 - disabling memory compression me@home.spamsucks.ca (Király) - 2014-04-15 06:01 +0000
            Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 16:54 -0400
          Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 09:11 +0200
            Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-20 09:24 -0400
        Re: 10.9 - disabling memory compression Jolly Roger <jollyroger@pobox.com> - 2014-04-15 02:10 +0000
    Re: 10.9 - disabling memory compression Rick Jones <rick.jones2@hp.com> - 2014-04-14 23:32 +0000
      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-14 19:58 -0400
      Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 09:45 +0200
        Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-20 09:26 -0400
    Re: 10.9 - disabling memory compression Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-04-15 00:38 -0700
      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 16:58 -0400
    Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:32 +0000
      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 17:04 -0400
        Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-17 00:04 +0000
          Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 15:15 -0400
            Re: 10.9 - disabling memory compression android <here@there.was> - 2014-04-17 21:29 +0200
            Re: 10.9 - disabling memory compression android <here@there.was> - 2014-04-17 21:29 +0200
              Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 15:48 -0400
                Re: 10.9 - disabling memory compression android <here@there.was> - 2014-04-17 21:58 +0200
                  Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 16:07 -0400
                    Re: 10.9 - disabling memory compression billy@MIX.COM - 2014-04-19 16:06 +0000
                      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 12:37 -0400
                      Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-19 17:27 +0000
                      Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 08:33 +0200
                        Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-20 09:13 -0400
              Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-18 05:55 +0000
                Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-18 10:00 -0400
            Re: 10.9 - disabling memory compression JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-17 15:30 -0400
              Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 16:02 -0400
                Re: 10.9 - disabling memory compression android <here@there.was> - 2014-04-17 22:10 +0200
                  Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 16:33 -0400
                    Re: 10.9 - disabling memory compression Jolly Roger <jollyroger@pobox.com> - 2014-04-17 21:54 +0000
                      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 18:13 -0400
                        Re: 10.9 - disabling memory compression Jolly Roger <jollyroger@pobox.com> - 2014-04-17 23:59 +0000
                          Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-18 17:59 -0400
                            Re: 10.9 - disabling memory compression Jolly Roger <jollyroger@pobox.com> - 2014-04-19 17:27 +0000
                            Re: 10.9 - disabling memory compression Martin Frost me at invalid stanford daht edu <nospam@stanford.edu.invalid> - 2014-04-19 14:15 -0700
                              Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 18:06 -0400
                                Re: 10.9 - disabling memory compression Martin Frost me at invalid stanford daht edu <nospam@stanford.edu.invalid> - 2014-04-19 17:16 -0700
                                  Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 20:32 -0400
                                    Re: 10.9 - disabling memory compression JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-19 21:40 -0400
                                  Re: 10.9 - disabling memory compression Your Name <YourName@YourISP.com> - 2014-04-20 15:45 +1200
            Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-18 05:46 +0000
              Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-18 09:44 -0400
                Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-18 21:06 +0000
                  Re: 10.9 - disabling memory compression JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-18 17:21 -0400
                    Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-18 17:30 -0400
                    Re: 10.9 - disabling memory compression nospam <nospam@nospam.invalid> - 2014-04-18 18:49 -0400
                    Re: 10.9 - disabling memory compression billy@MIX.COM - 2014-04-19 16:33 +0000
                    Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 08:53 +0200
                      Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-20 09:22 -0400
                      Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-21 03:49 +0000
                  Re: 10.9 - disabling memory compression Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-18 17:24 -0400
                  Re: 10.9 - disabling memory compression Warren Oates <warren.oates@gmail.com> - 2014-04-18 17:25 -0400
                    Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-19 03:09 +0000
                      Re: 10.9 - disabling memory compression billy@MIX.COM - 2014-04-19 15:21 +0000
                        Re: 10.9 - disabling memory compression Warren Oates <warren.oates@gmail.com> - 2014-04-19 16:01 -0400
                    Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 10:47 +0200
                      Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-21 03:52 +0000
                        Re: 10.9 - disabling memory compression JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-21 04:26 -0400
                          Re: 10.9 - disabling memory compression Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-22 04:07 +0000
                            Re: 10.9 - disabling memory compression Warren Oates <warren.oates@gmail.com> - 2014-04-22 08:15 -0400
                        Re: 10.9 - disabling memory compression Warren Oates <warren.oates@gmail.com> - 2014-04-21 08:44 -0400
                  Re: 10.9 - disabling memory compression Paul Sture <nospam@sture.ch> - 2014-04-20 10:42 +0200
      Re: 10.9 - disabling memory compression billy@MIX.COM - 2014-04-19 16:37 +0000

Page 1 of 5  [1] 2 3 4 5  Next page →

#58520 — 10.9 - disabling memory compression

As most of you know, Mavericks has a nifty, fast and efficient memory 
compression scheme to more efficiently employ allocated but more or less 
dormant memory.  This really makes sense in Macs with 8 GB or less 
memory and is especially a boon to laptops as it, in the end, saves 
battery power (less swapping), (along with other features such as timer 
coalescing).

On my 24 GB iMac, I checked the status of the memory lately and despite 
running, at the time 4 OS' concurrently (OS X, Ubunutu, OpenSUSE and 
WinXP) the compressed memory at the time was a mere 2.1 MB - that is 
less than 1/100 of a percent of the installed memory while having about 
10 GB of free memory.

While the compression scheme is reputed to be very efficient (CPU wise) 
it seems needless on systems with a large amount of installed memory and 
esp. desktops that don't have an especial need to save the odd joule 
here and there.

Of course there are helpful people out there so I found these helpful 
commands:

AlansMac:~ alanbrowne$ sysctl -a vm.compressor_mode
vm.compressor_mode: 4
AlansMac:~ alanbrowne$

Compressor mode: 4 is "on".

To set it to 1 (off):

          sudo nvram boot-args="vm_compressor=1"

So I'm now running in that mode.

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [next] | [standalone]

#58524

Alan Browne <alan.browne@freelunchvideotron.ca> writes:

> Compressor mode: 4 is "on".
> 
> To set it to 1 (off):
> 
>           sudo nvram boot-args="vm_compressor=1"
> 
> So I'm now running in that mode.

How much memory are you using with it off?

Billy Y..
-- 
        sub     #'9+1   ,r0             ; convert ascii byte
	add     #9.+1   ,r0             ; to an integer
	bcc     20$                     ; not a number

[toc] | [prev] | [next] | [standalone]

#58530

On 2014.04.13, 13:57 , billy@MIX.COM wrote:
> Alan Browne <alan.browne@freelunchvideotron.ca> writes:
>
>> Compressor mode: 4 is "on".
>>
>> To set it to 1 (off):
>>
>>            sudo nvram boot-args="vm_compressor=1"
>>
>> So I'm now running in that mode.
>
> How much memory are you using with it off?

There's no discernible difference.  The point is not what is saved 
memory wise (on a system with so much memory) but that it's yet another 
process that executes for no advantage whatsoever.


-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58525

In article <hrWdnZbK8t3VK9fOnZ2dnUVZ_hudnZ2d@giganews.com>,
 Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:

> As most of you know, Mavericks has a nifty, fast and efficient memory 
> compression scheme to more efficiently employ allocated but more or less 
> dormant memory.  This really makes sense in Macs with 8 GB or less 
> memory and is especially a boon to laptops as it, in the end, saves 
> battery power (less swapping), (along with other features such as timer 
> coalescing).
> 
> On my 24 GB iMac, I checked the status of the memory lately and despite 
> running, at the time 4 OS' concurrently (OS X, Ubunutu, OpenSUSE and 
> WinXP) the compressed memory at the time was a mere 2.1 MB - that is 
> less than 1/100 of a percent of the installed memory while having about 
> 10 GB of free memory.
> 
> While the compression scheme is reputed to be very efficient (CPU wise) 
> it seems needless on systems with a large amount of installed memory and 
> esp. desktops that don't have an especial need to save the odd joule 
> here and there.
> 
> Of course there are helpful people out there so I found these helpful 
> commands:
> 
> AlansMac:~ alanbrowne$ sysctl -a vm.compressor_mode
> vm.compressor_mode: 4
> AlansMac:~ alanbrowne$
> 
> Compressor mode: 4 is "on".
> 
> To set it to 1 (off):
> 
>           sudo nvram boot-args="vm_compressor=1"
> 
> So I'm now running in that mode.

Hmm. There's a bunch of people (including my other half) complaining of 
getting "your computer is running out of application memory" errors that 
no one (certainly not anyone from Apple) knows how to fix. The basic 
Apple Duhfense League response seems to be "repair the the permissions." 
Yeah, right. Would this compressed memory thingie have ought to do with 
this? I haven't had the problem on the MacBook Pro with 4 gigs RAM, but 
the fancy new iMac (with 8 gigs) does it from time to time.
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#58529

On 2014-04-13, Warren Oates <warren.oates@gmail.com> wrote:
> In article <hrWdnZbK8t3VK9fOnZ2dnUVZ_hudnZ2d@giganews.com>,
>  Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>
>> As most of you know, Mavericks has a nifty, fast and efficient memory 
>> compression scheme to more efficiently employ allocated but more or less 
>> dormant memory.  This really makes sense in Macs with 8 GB or less 
>> memory and is especially a boon to laptops as it, in the end, saves 
>> battery power (less swapping), (along with other features such as timer 
>> coalescing).
>> 
>> On my 24 GB iMac, I checked the status of the memory lately and despite 
>> running, at the time 4 OS' concurrently (OS X, Ubunutu, OpenSUSE and 
>> WinXP) the compressed memory at the time was a mere 2.1 MB - that is 
>> less than 1/100 of a percent of the installed memory while having about 
>> 10 GB of free memory.
>> 
>> While the compression scheme is reputed to be very efficient (CPU wise) 
>> it seems needless on systems with a large amount of installed memory and 
>> esp. desktops that don't have an especial need to save the odd joule 
>> here and there.
>> 
>> Of course there are helpful people out there so I found these helpful 
>> commands:
>> 
>> AlansMac:~ alanbrowne$ sysctl -a vm.compressor_mode
>> vm.compressor_mode: 4
>> AlansMac:~ alanbrowne$
>> 
>> Compressor mode: 4 is "on".
>> 
>> To set it to 1 (off):
>> 
>>           sudo nvram boot-args="vm_compressor=1"
>> 
>> So I'm now running in that mode.
>
> Hmm. There's a bunch of people (including my other half) complaining of 
> getting "your computer is running out of application memory" errors that 
> no one (certainly not anyone from Apple) knows how to fix. The basic 
> Apple Duhfense League response seems to be "repair the the permissions." 
> Yeah, right. Would this compressed memory thingie have ought to do with 
> this? I haven't had the problem on the MacBook Pro with 4 gigs RAM, but 
> the fancy new iMac (with 8 gigs) does it from time to time.

I've been wondering about this in conjunction with the VMs I'm running.
If I don't do anything in a running VM for several hours it's hard to
get its full attention back.  For example I can be playing music in a
Linux VM for hours on end but when I switch focus to it and try to do
something on the command line it takes ages for that bit to spring into
life.  I didn't see this before Mavericks so wondered if the bits of
the VM not being currently used have been compressed and the delay is
in bringing them back.

Dunno, just a theory, and maybe it's addressed in VMware Fusion 6, but since
VMware refuse to tell me what improvements that actually brings apart from
"it's better", the money is staying in my wallet thanks.

P.S.  I also noticed that if you go into Finder, highlight an app and
hit cmd-I the resulting Info window displays an item called "Prevent App
Nap".  I did try checking this on the Fusion app but didn't see any
difference, so cleared it again.  Does anyone know more about this feature?

-- 
Paul Sture

The final step of #heartbleed recovery is to call your mother, and advise
her to change her maiden name                                  -- @gojomo

[toc] | [prev] | [next] | [standalone]

#58535

On 2014.04.13, 15:18 , Paul Sture wrote:
> On 2014-04-13, Warren Oates <warren.oates@gmail.com> wrote:
>> In article <hrWdnZbK8t3VK9fOnZ2dnUVZ_hudnZ2d@giganews.com>,
>>   Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>>
>>> As most of you know, Mavericks has a nifty, fast and efficient memory
>>> compression scheme to more efficiently employ allocated but more or less
>>> dormant memory.  This really makes sense in Macs with 8 GB or less
>>> memory and is especially a boon to laptops as it, in the end, saves
>>> battery power (less swapping), (along with other features such as timer
>>> coalescing).
>>>
>>> On my 24 GB iMac, I checked the status of the memory lately and despite
>>> running, at the time 4 OS' concurrently (OS X, Ubunutu, OpenSUSE and
>>> WinXP) the compressed memory at the time was a mere 2.1 MB - that is
>>> less than 1/100 of a percent of the installed memory while having about
>>> 10 GB of free memory.
>>>
>>> While the compression scheme is reputed to be very efficient (CPU wise)
>>> it seems needless on systems with a large amount of installed memory and
>>> esp. desktops that don't have an especial need to save the odd joule
>>> here and there.
>>>
>>> Of course there are helpful people out there so I found these helpful
>>> commands:
>>>
>>> AlansMac:~ alanbrowne$ sysctl -a vm.compressor_mode
>>> vm.compressor_mode: 4
>>> AlansMac:~ alanbrowne$
>>>
>>> Compressor mode: 4 is "on".
>>>
>>> To set it to 1 (off):
>>>
>>>            sudo nvram boot-args="vm_compressor=1"
>>>
>>> So I'm now running in that mode.
>>
>> Hmm. There's a bunch of people (including my other half) complaining of
>> getting "your computer is running out of application memory" errors that
>> no one (certainly not anyone from Apple) knows how to fix. The basic
>> Apple Duhfense League response seems to be "repair the the permissions."
>> Yeah, right. Would this compressed memory thingie have ought to do with
>> this? I haven't had the problem on the MacBook Pro with 4 gigs RAM, but
>> the fancy new iMac (with 8 gigs) does it from time to time.
>
> I've been wondering about this in conjunction with the VMs I'm running.
> If I don't do anything in a running VM for several hours it's hard to
> get its full attention back.  For example I can be playing music in a
> Linux VM for hours on end but when I switch focus to it and try to do
> something on the command line it takes ages for that bit to spring into
> life.  I didn't see this before Mavericks so wondered if the bits of
> the VM not being currently used have been compressed and the delay is
> in bringing them back.

Today I've had 3 OS' running in Fusion (v 5.x) and left alone for quite 
a while - all 3 are immediately responsive on return (regardless of the 
mem compression flag.  Again I have a lot of memory on this iMac.

> Dunno, just a theory, and maybe it's addressed in VMware Fusion 6, but since
> VMware refuse to tell me what improvements that actually brings apart from
> "it's better", the money is staying in my wallet thanks.

:-)

> P.S.  I also noticed that if you go into Finder, highlight an app and
> hit cmd-I the resulting Info window displays an item called "Prevent App
> Nap".  I did try checking this on the Fusion app but didn't see any
> difference, so cleared it again.  Does anyone know more about this feature?

Never noticed it before.  Thanks.  I'll play with it  -  but I doubt it 
will improve things much on this Mac.  I'd _want_ it running on my SO's MBA.

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58531

On 2014.04.13, 14:50 , Warren Oates wrote:
> In article <hrWdnZbK8t3VK9fOnZ2dnUVZ_hudnZ2d@giganews.com>,
> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>
>> As most of you know, Mavericks has a nifty, fast and efficient memory
>> compression scheme to more efficiently employ allocated but more or
>> less dormant memory.  This really makes sense in Macs with 8 GB or
>> less memory and is especially a boon to laptops as it, in the end,
>> saves battery power (less swapping), (along with other features such
>> as timer coalescing).
>>
>> On my 24 GB iMac, I checked the status of the memory lately and
>> despite running, at the time 4 OS' concurrently (OS X, Ubunutu,
>> OpenSUSE and WinXP) the compressed memory at the time was a mere 2.1
>> MB - that is less than 1/100 of a percent of the installed memory
>> while having about 10 GB of free memory.
>>
>> While the compression scheme is reputed to be very efficient (CPU
>> wise) it seems needless on systems with a large amount of installed
>> memory and esp. desktops that don't have an especial need to save the
>> odd joule here and there.
>>
>> Of course there are helpful people out there so I found these helpful
>> commands:
>>
>> AlansMac:~ alanbrowne$ sysctl -a vm.compressor_mode
>> vm.compressor_mode: 4
>> AlansMac:~ alanbrowne$
>>
>> Compressor mode: 4 is "on".
>>
>> To set it to 1 (off):
>>
>>           sudo nvram boot-args="vm_compressor=1"
>>
>> So I'm now running in that mode.
>
> Hmm. There's a bunch of people (including my other half) complaining of
> getting "your computer is running out of application memory" errors that
> no one (certainly not anyone from Apple) knows how to fix. The basic
> Apple Duhfense League response seems to be "repair the the permissions."
> Yeah, right. Would this compressed memory thingie have ought to do with
> this? I haven't had the problem on the MacBook Pro with 4 gigs RAM, but
> the fancy new iMac (with 8 gigs) does it from time to time.

No idea - my instinct would be that with 8 GB (or certainly 4 GB) or 
less, to leave the compression on.

OTOH, turning it off (and back on again replacing the "1" with a "4") is 
trivial enough to try out (requires restarting of course).

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58534

In article <srydnWyjLYQUetfOnZ2dnUVZ_hidnZ2d@giganews.com>,
 Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:

> 
> No idea - my instinct would be that with 8 GB (or certainly 4 GB) or 
> less, to leave the compression on.
> 
> OTOH, turning it off (and back on again replacing the "1" with a "4") is 
> trivial enough to try out (requires restarting of course).

I've set it to "off" (and rebooted). See what happens.
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#58541

In article <534adc8b$0$18926$c3e8da3$cc4fe22d@news.astraweb.com>,
Warren Oates <warren.oates@gmail.com> wrote:

> Hmm. There's a bunch of people (including my other half) complaining of 
> getting "your computer is running out of application memory" errors that 
> no one (certainly not anyone from Apple) knows how to fix. The basic 
> Apple Duhfense League response seems to be "repair the the permissions." 
> Yeah, right. Would this compressed memory thingie have ought to do with 
> this? I haven't had the problem on the MacBook Pro with 4 gigs RAM, but 
> the fancy new iMac (with 8 gigs) does it from time to time.

Housekeeping? You can quit a PC app from a window. You need to quit an
app with the Mac from the menu or command-q. My wife, who uses a PC at
work and a Mac at home, instinctively closes a window with that red dot
and assumes that the app has quit. She's getting better.
Get a whole bunch of dormant apps and associated limbo files and memory
becomes an issue regardless of compression. Restart works well. Just a
thought.

leo

[toc] | [prev] | [next] | [standalone]

#58542

In article <130420141935099966%leoblaisdell@sbcglobal.net>, Leonard
Blaisdell <leoblaisdell@sbcglobal.net> wrote:
> In article <534adc8b$0$18926$c3e8da3$cc4fe22d@news.astraweb.com>,
> Warren Oates <warren.oates@gmail.com> wrote:
> > 
> > Hmm. There's a bunch of people (including my other half) complaining of 
> > getting "your computer is running out of application memory" errors that 
> > no one (certainly not anyone from Apple) knows how to fix. The basic 
> > Apple Duhfense League response seems to be "repair the the permissions." 
> > Yeah, right. Would this compressed memory thingie have ought to do with 
> > this? I haven't had the problem on the MacBook Pro with 4 gigs RAM, but 
> > the fancy new iMac (with 8 gigs) does it from time to time.
> 
> Housekeeping? You can quit a PC app from a window. You need to quit an
> app with the Mac from the menu or command-q. My wife, who uses a PC at
> work and a Mac at home, instinctively closes a window with that red dot
> and assumes that the app has quit. She's getting better.
> Get a whole bunch of dormant apps and associated limbo files and memory
> becomes an issue regardless of compression. Restart works well. Just a
> thought.

I don't know whether they work with Mavericks, but there are at least a
couple of add-ons that auto-quit applications when the last window is
closed.

   - RedQuits
     https://www.macupdate.com/app/mac/39814/redquits

   - StopLight
     http://lifehacker.com/202621/download-of-the-day-stoplight-mac

Of course, that is a nuisance when you want to clse the last window and
open another or create a new one.

[toc] | [prev] | [next] | [standalone]

#58545

On 2014.04.14, 00:34 , Your Name wrote:

> I don't know whether they work with Mavericks, but there are at least a
> couple of add-ons that auto-quit applications when the last window is
> closed.
>
>     - RedQuits
>       https://www.macupdate.com/app/mac/39814/redquits
>
>     - StopLight
>       http://lifehacker.com/202621/download-of-the-day-stoplight-mac
>
> Of course, that is a nuisance when you want to clse the last window and
> open another or create a new one.

Just remember CMD-Q.  Not very hard at all.


-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58712

On 2014-04-14, Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
> On 2014.04.14, 00:34 , Your Name wrote:
>
>> I don't know whether they work with Mavericks, but there are at least a
>> couple of add-ons that auto-quit applications when the last window is
>> closed.
>>
>>     - RedQuits
>>       https://www.macupdate.com/app/mac/39814/redquits
>>
>>     - StopLight
>>       http://lifehacker.com/202621/download-of-the-day-stoplight-mac
>>
>> Of course, that is a nuisance when you want to clse the last window and
>> open another or create a new one.
>
> Just remember CMD-Q.  Not very hard at all.

But occasionally too easy to hit when I'm aiming for Cmd-W :-(

-- 
Paul Sture

The final step of #heartbleed recovery is to call your mother, and advise
her to change her maiden name                                  -- @gojomo

[toc] | [prev] | [next] | [standalone]

#58723

On 2014.04.20, 04:53 , Paul Sture wrote:
> On 2014-04-14, Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>> On 2014.04.14, 00:34 , Your Name wrote:
>>
>>> I don't know whether they work with Mavericks, but there are at least a
>>> couple of add-ons that auto-quit applications when the last window is
>>> closed.
>>>
>>>      - RedQuits
>>>        https://www.macupdate.com/app/mac/39814/redquits
>>>
>>>      - StopLight
>>>        http://lifehacker.com/202621/download-of-the-day-stoplight-mac
>>>
>>> Of course, that is a nuisance when you want to clse the last window and
>>> open another or create a new one.
>>
>> Just remember CMD-Q.  Not very hard at all.
>
> But occasionally too easy to hit when I'm aiming for Cmd-W :-(

Yep


-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58543

In article <130420141935099966%leoblaisdell@sbcglobal.net>,
 Leonard Blaisdell <leoblaisdell@sbcglobal.net> wrote:

> In article <534adc8b$0$18926$c3e8da3$cc4fe22d@news.astraweb.com>,
> Warren Oates <warren.oates@gmail.com> wrote:
> 
> > Hmm. There's a bunch of people (including my other half) complaining of 
> > getting "your computer is running out of application memory" errors that 
> > no one (certainly not anyone from Apple) knows how to fix. The basic 
> > Apple Duhfense League response seems to be "repair the the permissions." 
> > Yeah, right. Would this compressed memory thingie have ought to do with 
> > this? I haven't had the problem on the MacBook Pro with 4 gigs RAM, but 
> > the fancy new iMac (with 8 gigs) does it from time to time.
> 
> Housekeeping? You can quit a PC app from a window. You need to quit an
> app with the Mac from the menu or command-q. My wife, who uses a PC at
> work and a Mac at home, instinctively closes a window with that red dot
> and assumes that the app has quit. She's getting better.
> Get a whole bunch of dormant apps and associated limbo files and memory
> becomes an issue regardless of compression. Restart works well. Just a
> thought.
> 
> leo

That's not what's going on here. 'Tis true the oul 'Woman leaves more 
stuff open than she should, but we've always had Macs and she's been 
doing it since System 6 (which is the last time we regularly saw that 
'out of memory' thing). This is something brand new that started with 
Mavericks on the new iMac.

There's a big long thread about it here:

https://discussions.apple.com/thread/5474263?tstart=0

with the usual ADF stuff about "third-party" apps and "how big is your 
hard drive" and just about anything to deny any problems exist ever on 
the Blessed Platform. Some people blame Mail while an iMovie update 
fixed the problem for others, but we don't use iMovie ever; some people 
had problems with the Calendar cache, but we don't use that either 
(BusyCal).
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#58569

In message <534bcbe0$0$9662$c3e8da3$aae71a0a@news.astraweb.com> 
  Warren Oates <warren.oates@gmail.com> wrote:
> https://discussions.apple.com/thread/5474263?tstart=0

I haven't seen this one. What I get on my iMac on occasion is "too many
file handlers" errors. The only fix I've found is rebooting.

Only happens on the iMac, but it is the computer working the hardest and
messing with the most files.

-- 
You couldn't say, 'I had orders.' You couldn't say, 'It's not fair.' No
one was listening. There were no Words. You owned yourself.  ...  Not
Thou Shalt Not. Say I Will Not. --Feet of Clay

[toc] | [prev] | [next] | [standalone]

#58544

On 2014.04.13, 22:35 , Leonard Blaisdell wrote:

> Housekeeping? You can quit a PC app from a window. You need to quit an
> app with the Mac from the menu or command-q.

Not always so.  There are a variety of apps that shut off on closing the 
window (red button).  The calculator and the App Store being a couple of 
them.  There are others.

The general approach is that an app is not running "in its window" but 
that its windows are extensions to the app.  But that doesn't apply in 
all cases.

Further, app that run in a terminal window will be force quit if the 
terminal window they are running in is closed.


My wife, who uses a PC at
> work and a Mac at home, instinctively closes a window with that red dot
> and assumes that the app has quit. She's getting better.
> Get a whole bunch of dormant apps and associated limbo files and memory
> becomes an issue regardless of compression. Restart works well. Just a
> thought.

CMD-Q or dock bar quitting doesn't require that much ... memory ... on 
the part of the user.  What doesn't help is that Lion (or ML) and later 
blue dots on the dock are so much harder to see than in the prior dock. 
  Not sure what possesses Apple to do these things.

You can also CMD-Tab through the apps and when an app you want to shut 
down is boxed, while continuing to hold down CMD, hit Q instead of tab 
to quit the app (or W to simply close the window)...

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58546

On 14-04-14 16:30, Alan Browne wrote:

> Further, app that run in a terminal window will be force quit if the 
> terminal window they are running in is closed.

Not sure if a character cell application is told to quit, or whether its
process is just unceremoniously euthanised when the parent process is
killed.

[toc] | [prev] | [next] | [standalone]

#58547

On 2014.04.14, 17:36 , JF Mezei wrote:
> On 14-04-14 16:30, Alan Browne wrote:
>
>> Further, app that run in a terminal window will be force quit if the
>> terminal window they are running in is closed.
>
> Not sure if a character cell application is told to quit, or whether its
> process is just unceremoniously euthanised when the parent process is
> killed.

The later I think - since a terminal run program receives no signals 
other than the keyboard or perhaps pipes.  But if you bg the program and 
make sure it has somewhere to dump its output, then it will keep running.

$ ./aprogram > ~/datadump/x.file &
$ exit

then close the window.


-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58708

On 2014-04-14, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 14-04-14 16:30, Alan Browne wrote:
>
>> Further, app that run in a terminal window will be force quit if the 
>> terminal window they are running in is closed.
>
> Not sure if a character cell application is told to quit, or whether its
> process is just unceremoniously euthanised when the parent process is
> killed.

Terminal Preferences -> Basic -> Shell 

Prompt before closing:
    * Always
    * Never
    * Only if there are processes other than the login shell and:

and below that you can specify additional processes to be checked against.

-- 
Paul Sture

The final step of #heartbleed recovery is to call your mother, and advise
her to change her maiden name                                  -- @gojomo

[toc] | [prev] | [next] | [standalone]

#58551

Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> Not always so.  There are a variety of apps that shut off on closing the 
> window (red button).  The calculator and the App Store being a couple of 
> them.  There are others.

The general guideline is that an edit-a-document app (TextEdit, Preview, 
Pages, basically apps that do nothing without an open document) will 
stay open afer all of its windows (i.e. documents) are closed. An app 
that isn't document based (Disk Utility, Contacts, Dictionary) will quit 
when its (usually single and does everything) window is closed.

-- 
K.

Lang may your lum reek.

[toc] | [prev] | [next] | [standalone]

Page 1 of 5  [1] 2 3 4 5  Next page →

Back to top | Article view | comp.sys.mac.system

csiph-web