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

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

Startup disk has no more space available.

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

Contents

  Startup disk has no more space available. Tom Evans <tomevans9890@yahoo.ca> - 2014-11-30 09:02 -0800
    Re: Startup disk has no more space available. JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-11-30 14:12 -0500
      Re: Startup disk has no more space available. Tom Evans <tomevans9890@yahoo.ca> - 2014-11-30 11:58 -0800
        Re: Startup disk has no more space available. JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-11-30 16:24 -0500
        Re: Startup disk has no more space available. Walter Bushell <proto@panix.com> - 2014-12-08 08:33 -0500
      Re: Startup disk has no more space available. Tom Evans <tomevans9890@yahoo.ca> - 2014-11-30 12:11 -0800
        Re: Startup disk has no more space available. billy@MIX.COM - 2014-11-30 23:18 +0000
        Re: Startup disk has no more space available. John Albert <j.albert@snet.net> - 2014-12-10 15:49 -0500
          Re: Startup disk has no more space available. nospam <nospam@nospam.invalid> - 2014-12-10 16:46 -0500
            Re: Startup disk has no more space available. Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-12-14 12:34 -0500
              Re: Startup disk has no more space available. JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-12-14 14:58 -0500
              Re: Startup disk has no more space available. nospam <nospam@nospam.invalid> - 2014-12-14 15:20 -0500
                Re: Startup disk has no more space available. Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-12-15 16:24 -0500
                Re: Startup disk has no more space available. Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-12-16 22:29 -0800
                  Re: Startup disk has no more space available. nospam <nospam@nospam.invalid> - 2014-12-17 01:37 -0500
                    Re: Startup disk has no more space available. Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-12-17 20:26 -0800
                      Re: Startup disk has no more space available. Tim Streater <timstreater@greenbee.net> - 2014-12-18 09:06 +0000
                  Re: Startup disk has no more space available. Jolly Roger <jollyroger@pobox.com> - 2014-12-18 14:45 +0000
          Re: Startup disk has no more space available. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-12-11 01:49 +0000
            Re: Startup disk has no more space available. JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-12-11 00:58 -0500
              Re: Startup disk has no more space available. John Albert <j.albert@snet.net> - 2014-12-11 17:18 -0500
                Re: Startup disk has no more space available. nospam <nospam@nospam.invalid> - 2014-12-11 17:24 -0500
                Re: Startup disk has no more space available. JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-12-11 22:47 -0500
              Re: Startup disk has no more space available. Paul Sture <nospam@sture.ch> - 2014-12-14 10:49 +0100
                Re: Startup disk has no more space available. Huge <Huge@nowhere.much.invalid> - 2014-12-14 12:13 +0000
              Re: Startup disk has no more space available. Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-12-14 12:27 -0500
      Re: Startup disk has no more space available. billy@MIX.COM - 2014-11-30 23:16 +0000

Page 1 of 2  [1] 2  Next page →

#67491 — Startup disk has no more space available.

When I came to my Mac this morning, my computer was slow to awake, and 
Activity Monitor window showed this message:

"Your Mac OS startup disk has no more space available for application memory."

I restarted.  After restarting, my page-ins are about eight gigabytes 
and my page-outs are still over 21 gigabytes.

Activity Monitor > Disk Usage shows almost 200 gigabytes are free out 
of one terabyte.

Actiivty Monitor > Real Mem shows the biggest users now are Safari Web 
Content (580 MB), Flash Player (287 MB) and Safari (187 MB).

I have 16 gigs of RAM -- the maximum for my desktop 2011 Imac.

OS 10.6.8.

[toc] | [next] | [standalone]

#67492

On 14-11-30 12:02, Tom Evans wrote:

> "Your Mac OS startup disk has no more space available for application memory."
> 
> I restarted.  After restarting, my page-ins are about eight gigabytes 
> and my page-outs are still over 21 gigabytes.

> Activity Monitor > Disk Usage shows almost 200 gigabytes are free out 
> of one terabyte.

from terminal,
Try ls -l /private/var/vm

This is the directory where the page/swap files are located. See if
there is anything really funky in it.

You could try to boot into single user mode and delete the swapfiles and
and you reboot, OS-X would rebuild new ones from scratch.

note: when you boot into ingle user mode, you'll see instructions on how
to mount the disk so you can write to it, you need to do that to start
to delete files.

You may not be able to delete all swapfiles if one is already in use by
single user mode.

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

#67493

On 2014-11-30 11:12:00 -0800, JF Mezei said:

> On 14-11-30 12:02, Tom Evans wrote:
> 
>> "Your Mac OS startup disk has no more space available for application memory."
>> 
>> I restarted.  After restarting, my page-ins are about eight gigabytes
>> and my page-outs are still over 21 gigabytes.
> 
>> Activity Monitor > Disk Usage shows almost 200 gigabytes are free out
>> of one terabyte.
> 
> from terminal,
> Try ls -l /private/var/vm
> 
> This is the directory where the page/swap files are located. See if
> there is anything really funky in it.
> 
> You could try to boot into single user mode and delete the swapfiles and
> and you reboot, OS-X would rebuild new ones from scratch.
> 
> note: when you boot into ingle user mode, you'll see instructions on how
> to mount the disk so you can write to it, you need to do that to start
> to delete files.
> 
> You may not be able to delete all swapfiles if one is already in use by
> single user mode.

Thanks, J.P.

Is there any easier, low-risk way to solve the problem?

I don't know how to use Terminal, so I'd risk exacerating the problem.  
You wrote "See if there is anything really funky" in the directory.  I 
don't know what would look funky and how to deal with funk that I might 
find, without worsening the problem.

Also I've never used single-user mode, so that also sounds frightening. 
 I just found a video on Youtube that advises people not to use 
single-user mode if they're not familiar with it, because if one makes 
a typing error in Terminal, one can accidentally erase one's drive.

Tom

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

#67497

On 14-11-30 14:58, Tom Evans wrote:

>> from terminal,
>> Try ls -l /private/var/vm

> Is there any easier, low-risk way to solve the problem?

terminal is lower risk than GUI because the GUI tries very hard to hide
things from you.  You just have to read your command before you press
return to make sure you are asking it to do what you want it to do.

> You wrote "See if there is anything really funky" in the directory.  I 
> don't know what would look funky and how to deal with funk that I might 
> find, without worsening the problem.

If you see a whole lot of files taking up a whole lot of space, this is
funky. If you see 3 to 5 files, it would be OK. However, what you may
not see is some page file that has grown to a point where it can't grow
anymore (not sure if there is a limit for extents on HFS+) and the
message you got was because it tried to grow a pagefile and couldn't.
Deleting it would cause it to be recreated from scratch with
brandspanking new continuous allocation, all shiny and clean.


> Also I've never used single-user mode, so that also sounds frightening. 

Think of it as a minimal boot. You get to terminal mode automatically
with limited editing. The reason is to make sure that the OS hasn't had
time to open/lock those page files yet.

reboot, press COMMAND-S while it starts booting. This gets you to single
user mode.

You'll see these instructions on screen to allow the disk to be modified:

/sbin/fsck -fy
/sbin/mount -uw

The first command checks integrity of your disk, the second one mounts
it read/write. (in single user mode, the disks are first mounted read-only)

then:
cd /private/var/vm
ls -l

This will give you a list of swap files, as well as a sleep image
(depending on your system options).

output such as:
bike:~ $   ls -l -T
total 50855936
-rw------T  1 root  wheel  25769803776 Sep  8 03:20:31 2014 sleepimage
-rw-------  1 root  wheel     67108864 Nov 25 15:05:37 2014 swapfile0
-rw-------  1 root  wheel     67108864 Nov 29 03:20:44 2014 swapfile1
-rw-------  1 root  wheel    134217728 Nov 29 03:20:44 2014 swapfile2

-l is the long list, -T also prints the year and full time. If you see
files that are not this year, it means they can be deleted.

You can delete those files:

rm -v swapfile*

(the -v is the verbose mode, will list the files being deleted).

then "exit" or "reboot" and your system will reboot normally. It will
recreate the files as necessary.

Now, normally, you would never have to or want to do this. But the
message you got indicates that OS-X had problem mapping your application
memory to a swapfile. This should normally never happen. And I have seen
cases where the swapfiles don't actually all get deleted at reboot and
old ones are leftover for a long time. (depending on OS version).

>  I just found a video on Youtube that advises people not to use 
> single-user mode if they're not familiar with it, because if one makes 
> a typing error in Terminal, one can accidentally erase one's drive.

You'd have to be that chimpanze that writes shakespear by chance on a
typewriter.  if you "cd" to a directory such as /private/var/vm  , you'd
have to be really drunk to type something like rm -R -v /*/*.* instead
of rm -v swapfile*

note: when in single user mode, you are the all mighty root with all
powers and privileges. So yes, you have to be careful and not play around.

However, to investigate a problem and make a targeted change, it is fine.

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

#67583

In article <2014113011585524984-tomevans9890@yahooca>,
 Tom Evans <tomevans9890@yahoo.ca> wrote:

> Also I've never used single-user mode, so that also sounds frightening. 
>  I just found a video on Youtube that advises people not to use 
> single-user mode if they're not familiar with it, because if one makes 
> a typing error in Terminal, one can accidentally erase one's drive.
> 
> Tom

Be very careful and make a backup before proceeding.

-- 
Never attribute to stupidity that which can be explained by greed. Me.

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

#67496

On 2014-11-30 11:12:00 -0800, JF Mezei said:

> On 14-11-30 12:02, Tom Evans wrote:
> 
>> "Your Mac OS startup disk has no more space available for application memory."
>> 
>> I restarted.  After restarting, my page-ins are about eight gigabytes
>> and my page-outs are still over 21 gigabytes.
> 
>> Activity Monitor > Disk Usage shows almost 200 gigabytes are free out
>> of one terabyte.
> 
> from terminal,
> Try ls -l /private/var/vm
> 
> This is the directory where the page/swap files are located. See if
> there is anything really funky in it.
> 
> You could try to boot into single user mode and delete the swapfiles and
> and you reboot, OS-X would rebuild new ones from scratch.
> 
> note: when you boot into ingle user mode, you'll see instructions on how
> to mount the disk so you can write to it, you need to do that to start
> to delete files.
> 
> You may not be able to delete all swapfiles if one is already in use by
> single user mode.

I just solved the problem by restarting for the second time today.

This time the page-outs returned to zero after restarting.

What a relief!

Thanks.

Tom

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

#67504

Tom Evans <tomevans9890@yahoo.ca> writes:

> I just solved the problem by restarting for the second time today.
> 
> This time the page-outs returned to zero after restarting.

I don'tknow that there's any difference, but when something
like comes up for me, I've had better luck with a shutdown
than a restart (while the hardware remains powered up).

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]

#67590

On 11/30/14 3:11 PM, Tom Evans wrote:
> I just solved the problem by restarting for the second time today.
>
> This time the page-outs returned to zero after restarting.

I "solved" excessive page-outs and disk activity in Yosemite by
- disabling swap (turning off VM)
- disabling compressed memory
- disabling spotlight
- also disabled hibernation mode (not related to page outs)

This is on a 2012 Mac Mini with 10gb of RAM.

No problems running without any VM or swap -- runs great using the old 
"Classic Mac" paradigm (when you run out of RAM = crash!)

Not a single crash after setting up to run this way.
Runs cleaner and FASTER than before.

And this is booting from Yosemite installed on an -ancient- 4200rpm 2.5" 
IDE drive mounted in an external firewire400 enclosure!

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

#67591

In article <5488b1b7$0$26703$2c56edd9@usenetrocket.com>, John Albert
<j.albert@snet.net> wrote:

> > I just solved the problem by restarting for the second time today.
> >
> > This time the page-outs returned to zero after restarting.
> 
> I "solved" excessive page-outs and disk activity in Yosemite by
> - disabling swap (turning off VM)
> - disabling compressed memory
> - disabling spotlight
> - also disabled hibernation mode (not related to page outs)

all but the last one are a *really* bad idea. very, very bad.

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

#67616

On 2014.12.10, 16:46 , nospam wrote:
> In article <5488b1b7$0$26703$2c56edd9@usenetrocket.com>, John Albert
> <j.albert@snet.net> wrote:
>
>>> I just solved the problem by restarting for the second time today.
>>>
>>> This time the page-outs returned to zero after restarting.
>>
>> I "solved" excessive page-outs and disk activity in Yosemite by
>> - disabling swap (turning off VM)
>> - disabling compressed memory
>> - disabling spotlight
>> - also disabled hibernation mode (not related to page outs)
>
> all but the last one are a *really* bad idea. very, very bad.

Horseshit.

Compression is easily turned off and has no effect on operations.  Gone 
weeks and weeks without it active.

I haven't turned off swap, but with the memory on this machine it should 
not be an issue.  I typically have in excess of 8 GB of RAM available. 
(Right now with nothing but browsers, calendars, usenet, and other light 
apps I have over 15 GB available).

When I have the time to screw around I'll turn off the VM too and see 
how that flies.

-- 
<< Among Broad Outlines, conception is far more pleasurable
    than “carrying [the children] to fruition.”
    Sadly, “there’s a high infant mortality rate among
    Broad Outlines—they often fall prey to Nonstarters.” >>
                       "Bestiary of Intelligence Writing" - CIA

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

#67618

On 14-12-14 12:34, Alan Browne wrote:
> When I have the time to screw around I'll turn off the VM too and see 
> how that flies.

Note, turning off swap/page files does not turn off virtual memory. The
mapping of a process' address space to actual physical RAM address space
continues. Without virtual memory, you can't have shared code for
instance since it is needed to allow a process's address space to map an
area of what it thinks is its own code to physical RAM address that
contains the shared code.

It is also not clear to me if free-BSD/OS-X has memory protection at the
physical RAM level or only in the virtual memory table(s).


Turning off page/swap files is only useful when you run from
no-writeable disks. (such as when you boot from CD/DVD or perhaps the
recovery partition, but not sure about that).

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

#67620

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

> >> I "solved" excessive page-outs and disk activity in Yosemite by
> >> - disabling swap (turning off VM)
> >> - disabling compressed memory
> >> - disabling spotlight
> >> - also disabled hibernation mode (not related to page outs)
> >
> > all but the last one are a *really* bad idea. very, very bad.
> 
> Horseshit.
> 
> Compression is easily turned off and has no effect on operations.  Gone 
> weeks and weeks without it active.

memory compression reduces the need to swap, which speeds up the
computer.

if you have a huge amount of memory then the difference may not be
major, but it's not zero and not everyone has a huge amount of memory.
most don't, and they will notice a difference.

> I haven't turned off swap, but with the memory on this machine it should 
> not be an issue.  I typically have in excess of 8 GB of RAM available. 
> (Right now with nothing but browsers, calendars, usenet, and other light 
> apps I have over 15 GB available).

the more physical memory you have the longer you'll last without swap.
it *will* be a problem.

also, if you have 15 gig free, your system is not running properly. you
want as little free memory as possible. free memory is wasted memory.

> When I have the time to screw around I'll turn off the VM too and see 
> how that flies.

it's your time to waste.

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

#67640

On 2014.12.14, 15:20 , nospam wrote:
> In article <KpidnXmOcI2NVxDJnZ2dnUU7-IudnZ2d@giganews.com>, Alan Browne
> <alan.browne@FreelunchVideotron.ca> wrote:
>
>>>> I "solved" excessive page-outs and disk activity in Yosemite by
>>>> - disabling swap (turning off VM)
>>>> - disabling compressed memory
>>>> - disabling spotlight
>>>> - also disabled hibernation mode (not related to page outs)
>>>
>>> all but the last one are a *really* bad idea. very, very bad.
>>
>> Horseshit.
>>
>> Compression is easily turned off and has no effect on operations.  Gone
>> weeks and weeks without it active.
>
> memory compression reduces the need to swap, which speeds up the
> computer.
>
> if you have a huge amount of memory then the difference may not be
> major, but it's not zero and not everyone has a huge amount of memory.
> most don't, and they will notice a difference.

Point is I have so much memory that there are rarely swaps and they are 
small.  And not really needed.

Current time since boot is about 10.5 days with 7.5 MB swapped - and was 
not ever needed to be swapped.

>> I haven't turned off swap, but with the memory on this machine it should
>> not be an issue.  I typically have in excess of 8 GB of RAM available.
>> (Right now with nothing but browsers, calendars, usenet, and other light
>> apps I have over 15 GB available).
>
> the more physical memory you have the longer you'll last without swap.
> it *will* be a problem.

Nope.  I run for weeks without the available memory getting below about 
5 to 6 GB.  And that's pretty rare.  (Note that a variety of apps are 
memory hogs (Word, Excel, Fusion/WinXP, Photoshop/Bridge, etc.)  I can 
run it up by using a RAM disk pretty good but I only need that on occasion.

>
> also, if you have 15 gig free, your system is not running properly. you
> want as little free memory as possible. free memory is wasted memory.

Only as much is needed will be used.

And you always want some slack in order to avoid swapping.  It's my 
choice to overload the system with memory in order that swapping be 
reduced or eliminated in order to avoid beachballs.  If I see the free 
memory getting below about 4 GB very often I'll bump this iMac up to 32 GB.

>
>> When I have the time to screw around I'll turn off the VM too and see
>> how that flies.
>
> it's your time to waste.

It's called experimenting.  That's how you find out things.  Swapping is 
a nice and needed thing.  OTOH it's blown away with cheap memory.

Or the much more expensive stuff from Apple.

-- 
<< Among Broad Outlines, conception is far more pleasurable
    than “carrying [the children] to fruition.”
    Sadly, “there’s a high infant mortality rate among
    Broad Outlines—they often fall prey to Nonstarters.” >>
                       "Bestiary of Intelligence Writing" - CIA

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

#67665

In article <141220141520276016%nospam@nospam.invalid>,
 nospam <nospam@nospam.invalid> wrote:

> In article <KpidnXmOcI2NVxDJnZ2dnUU7-IudnZ2d@giganews.com>, Alan Browne
> <alan.browne@FreelunchVideotron.ca> wrote:
> 
> > >> I "solved" excessive page-outs and disk activity in Yosemite by
> > >> - disabling swap (turning off VM)
> > >> - disabling compressed memory
> > >> - disabling spotlight
> > >> - also disabled hibernation mode (not related to page outs)
> > >
> > > all but the last one are a *really* bad idea. very, very bad.
> > 
> > Horseshit.
> > 
> > Compression is easily turned off and has no effect on operations.  Gone 
> > weeks and weeks without it active.
> 
> memory compression reduces the need to swap, which speeds up the
> computer.

Not entirely.

Apple's recent virtual memory schemes leave a lot to be desired.  
Compression sets aside a large cache for compressed memory, and that 
large cache means there's less fast RAM for applications.  The cache is 
a total waste of time for memory that can't be compressed by the pager's 
algorithm.

Disabling swap in 10.7+ results in massive performance for apps that use 
lots of memory-mapped file I/O but not a lot of plain allocated memory.  
It seems to eliminate poor decisions about what purges first.  On the 
other hand, you're SOL if an app needs a lot of temporary memory and 
swap is disabled.

Disabling Spotlight for temp files is critical.  Poor old HFS+ can't 
handle so much use in modern times.

Or run Linux.


> if you have a huge amount of memory then the difference may not be
> major, but it's not zero and not everyone has a huge amount of memory.
> most don't, and they will notice a difference.
> 
> > I haven't turned off swap, but with the memory on this machine it should 
> > not be an issue.  I typically have in excess of 8 GB of RAM available. 
> > (Right now with nothing but browsers, calendars, usenet, and other light 
> > apps I have over 15 GB available).
> 
> the more physical memory you have the longer you'll last without swap.
> it *will* be a problem.
> 
> also, if you have 15 gig free, your system is not running properly. you
> want as little free memory as possible. free memory is wasted memory.
> 
> > When I have the time to screw around I'll turn off the VM too and see 
> > how that flies.
> 
> it's your time to waste.

-- 
I will not see posts from astraweb, theremailer, dizum, or google
because they host Usenet flooders.

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

#67666

In article <mcmurtrie-F13D1A.22290716122014@news.sonic.net>, Kevin
McMurtrie <mcmurtrie@pixelmemory.us> wrote:

> > > >> I "solved" excessive page-outs and disk activity in Yosemite by
> > > >> - disabling swap (turning off VM)
> > > >> - disabling compressed memory
> > > >> - disabling spotlight
> > > >> - also disabled hibernation mode (not related to page outs)
> > > >
> > > > all but the last one are a *really* bad idea. very, very bad.
> > > 
> > > Horseshit.
> > > 
> > > Compression is easily turned off and has no effect on operations.  Gone 
> > > weeks and weeks without it active.
> > 
> > memory compression reduces the need to swap, which speeds up the
> > computer.
> 
> Not entirely.
> 
> Apple's recent virtual memory schemes leave a lot to be desired.  
> Compression sets aside a large cache for compressed memory, and that 
> large cache means there's less fast RAM for applications.  The cache is 
> a total waste of time for memory that can't be compressed by the pager's 
> algorithm.
> 
> Disabling swap in 10.7+ results in massive performance for apps that use 
> lots of memory-mapped file I/O but not a lot of plain allocated memory.  
> It seems to eliminate poor decisions about what purges first.  On the 
> other hand, you're SOL if an app needs a lot of temporary memory and 
> swap is disabled.
> 
> Disabling Spotlight for temp files is critical.  Poor old HFS+ can't 
> handle so much use in modern times.
> 
> Or run Linux.

nonsense.

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

#67702

In article <171220140137466148%nospam@nospam.invalid>,
 nospam <nospam@nospam.invalid> wrote:

> In article <mcmurtrie-F13D1A.22290716122014@news.sonic.net>, Kevin
> McMurtrie <mcmurtrie@pixelmemory.us> wrote:
> 
> > > > >> I "solved" excessive page-outs and disk activity in Yosemite by
> > > > >> - disabling swap (turning off VM)
> > > > >> - disabling compressed memory
> > > > >> - disabling spotlight
> > > > >> - also disabled hibernation mode (not related to page outs)
> > > > >
> > > > > all but the last one are a *really* bad idea. very, very bad.
> > > > 
> > > > Horseshit.
> > > > 
> > > > Compression is easily turned off and has no effect on operations.  Gone 
> > > > weeks and weeks without it active.
> > > 
> > > memory compression reduces the need to swap, which speeds up the
> > > computer.
> > 
> > Not entirely.
> > 
> > Apple's recent virtual memory schemes leave a lot to be desired.  
> > Compression sets aside a large cache for compressed memory, and that 
> > large cache means there's less fast RAM for applications.  The cache is 
> > a total waste of time for memory that can't be compressed by the pager's 
> > algorithm.
> > 
> > Disabling swap in 10.7+ results in massive performance for apps that use 
> > lots of memory-mapped file I/O but not a lot of plain allocated memory.  
> > It seems to eliminate poor decisions about what purges first.  On the 
> > other hand, you're SOL if an app needs a lot of temporary memory and 
> > swap is disabled.
> > 
> > Disabling Spotlight for temp files is critical.  Poor old HFS+ can't 
> > handle so much use in modern times.
> > 
> > Or run Linux.
> 
> nonsense.

I picture you as an old man who hasn't seen the inner workings of a 
computer since they were built with gears.

-- 
I will not see posts from astraweb, theremailer, dizum, or google
because they host Usenet flooders.

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

#67706

In article <mcmurtrie-980E33.20260417122014@news.sonic.net>, Kevin
McMurtrie <mcmurtrie@pixelmemory.us> wrote:

>I picture you as an old man who hasn't seen the inner workings of a 
>computer since they were built with gears.

Yeah but that had a production run of one and took 150 years to build.

-- 
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf

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

#67708

On 2014-12-17, Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote:
>
> Not entirely.
>
> Apple's recent virtual memory schemes leave a lot to be desired.  
> Compression sets aside a large cache for compressed memory, and that 
> large cache means there's less fast RAM for applications.  The cache is 
> a total waste of time for memory that can't be compressed by the pager's 
> algorithm.
>
> Disabling swap in 10.7+ results in massive performance for apps that use 
> lots of memory-mapped file I/O but not a lot of plain allocated memory.  
> It seems to eliminate poor decisions about what purges first.  On the 
> other hand, you're SOL if an app needs a lot of temporary memory and 
> swap is disabled.
>
> Disabling Spotlight for temp files is critical.  Poor old HFS+ can't 
> handle so much use in modern times.
>
> Or run Linux.

Here you go again. You've been trodding out this tired essay over and
over here for the past umpteen years, despite the fact that others
aren't seeing this mysterious problem you keep harping about like a
child with a grudge.  The fact is HFS+ and Mac OS X Yosemite work well
for the majority of use cases and the majority of Mac users. If this
so-called problem you keep mentioning over and over were a widespread
issue for everyone, I'd expect to see others echoing your rants. I'm
STILL not seeing that, and you've been at this a while. Don't you ever
get tired of holding this chip on your shoulder? Time to let it go and
move on.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

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

#67595

Okay, so one time? In band camp? John Albert <j.albert@snet.net> was all, like:
> On 11/30/14 3:11 PM, Tom Evans wrote:
>> I just solved the problem by restarting for the second time today.
>>
>> This time the page-outs returned to zero after restarting.

> I "solved" excessive page-outs and disk activity in Yosemite by
> - disabling swap (turning off VM)

Wow, that is a *terrible* idea.

> - disabling compressed memory

Ibid.

> - disabling spotlight

Well, that's just silly.

> This is on a 2012 Mac Mini with 10gb of RAM.

> No problems running without any VM or swap -- runs great using the old 
> "Classic Mac" paradigm (when you run out of RAM = crash!)

Yeah, that's "no problem". Right.

-- 
Thanks to the human heart by which we live,
Thanks to its tenderness, its joys, and fears,
To me the meanest flower that blows can give
Thoughts that do often lie too deep for tears

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

#67596

This thread has made me curious.

Where in Yosemite, does one turn off VM ?  I remember MacOS being able
to do that in early versions where it started to support VM. But haven't
seen this in ages.

I can see that if you turn off VM, page/swap files would no longer be
needed.  I could see that if you could limit total virtual memory space
to that of RAM, nothing would ever get paged out, but i am not even sure
this is possible, and if so, whether virtual memory space would be a per
process limit or system-wide limit.

Can a modern X86 64 bit chip run without virtual memory enabled ?

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web