Re:Fix random few-second freezes in Mountain Lion
by workbench on Monday April 29, 2013 @11:25AM
(#5626751)
If you're running things like iStat Menus then you shouldn't be shocked when the system runs sluggish at times.
[ Parent
| on HN ]
Re:Fix random few-second freezes in Mountain Lion
by JonnieCache on Monday April 29, 2013 @11:33AM
(#5626810)
Is it really that unrealistic in 2013 to expect my machine to be able to update a few graphs once every couple of seconds without falling to its knees and weeping? I know it's having to make lots of calls into the kernel to get the data, and I can live with it taking up a little bit of CPU now and then, but I have a right to expect it not to hang the OS.
I guess the ugly UI of the thing should have been a warning.
Re:Fix random few-second freezes in Mountain Lion
by coldtea on Monday April 29, 2013 @04:41PM
(#5628584)
>Is it really that unrealistic in 2013 to expect my machine to be able to update a few graphs once every couple of seconds without falling to its knees and weeping?
It depends on how it's coded. And stat apps are notorious for using lots of resources.
Otherwise, a 2013 machine is a pretty tough beast performance wise, including running tons of highly demanding apps.
For people that know about DAWs, this video proves that the Retina MBP 15" is an absolute beast:
Re:Fix random few-second freezes in Mountain Lion
by pavel_lishin on Monday April 29, 2013 @11:50AM
(#5626914)
I like their UI.
Re:Fix random few-second freezes in Mountain Lion
by JonnieCache on Monday April 29, 2013 @11:57AM
(#5626954)
Ugly is probably too harsh, you're right. However I find that amount of fiddly extra chrome sets off alarm bells in my head. The config app gives me flashbacks of trying to delete norton utilities.
Re:Fix random few-second freezes in Mountain Lion
by Osmium on Monday April 29, 2013 @05:02PM
(#5628742)
I run iStat Menus and have never noticed it cause even the slightest problem? I don't understand the problem?
The only thing that causes my MacBook to run slow is Dropbox when it does its re-indexing. 100% CPU, really? Sigh...