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.
Thread beginning with comment 515530
To read all comments associated with this story, please click here.
Same Problem in FreeBSD?
by puenktchen on Tue 24th Apr 2012 15:18 UTC
Member since:

The related implementation in FreeBSD seems to have a similar problem:

NetBSD users have also reported that UVM’s im- provements have had a positive effect on their applica- tions. This is most noticeable when physical memory becomes scarce and the VM system must page out data to free up memory. Under BSD VM this type of paging causes the system to become highly unresponsive, while under UVM the system slows while paging but does not become unresponsive.

Should be easy to fix: just start to page out some stuff in time before there is no memory left.

Reply Score: 2