Linked by Thom Holwerda on Mon 23rd Apr 2012 16:29 UTC
Mac OS X Adam Fields and Perry Metzger have been investigating the serious performance issues people are experiencing with Lion. "Frequent beachballs, general overall slowness and poor UI responsivness, specific and drastic slowdowns on every Time Machine run, high memory utilization in Safari Web Content, mds, and kernel_task processes, large numbers of page outs even with a good deal of available RAM, and high amounts of RAM marked as inactive which is not readily freed back to other applications, with page outs favored." Apparently the issue is that the "virtual memory manager is bad at managing which pages should be freed from the inactive state and which ones should be paged out to disk". I won't make myself popular with a certain part of our readership, but really, is this considered a new problem? Mac OS X has always had terrible memory management, and where Windows has continuously become better at it, Mac OS X seems to have been stagnant and even getting worse. This is what happens when the company earns 2/3s of its revenue somewhere else.
Permalink for comment 515425
To read all comments associated with this story, please click here.
It's the paging not the MM
by cybergorf on Mon 23rd Apr 2012 20:51 UTC
Member since:

My 2008 MacBookPro is running Lion, but I did not have these problems so far ... because I got more than enough RAM for my uses (6 GB).
But before my upgrade I used to have 2GB using Leopard and yes it was slow.
Now since I also put a SSD in this "old" laptop I turned off paging completely to avoid wearing and the OS became even more responsive (no not just the loading/saving but the overall feeling)

Paging is somewhat broken in OSX, but you can switch it off. For me paging is broken by concept anyway. For an old Amiga user it should be the other way round: don't page blocks of your RAM to the harddisk but have a RAMdisk for temp files and avoid unnecessary IO on your drive!

Edited 2012-04-23 20:57 UTC

Reply Score: 2