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 516445
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Software engineering VS coding
by zima on Mon 30th Apr 2012 23:57 UTC in reply to "Software engineering VS coding"
Member since:

A lot software these days seems to be developed not by highly trained engineers, but by coders [...] This is why the quality is so appalling.

Yeah, painful - but also don't mythologise the past too much. Bad code is around for a long time (maybe in how mostly the decent code survives, we remember it better)

The tide of Visual Basic is almost two decades old by now... (and I'm sure there were similar, earlier)

Reply Parent Score: 2