Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: How to disable (and enable) Dashboard' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: How to disable (and enable) Dashboard
Authored by: Pedro Estarque on Jul 30, '05 02:21:51PM

I hate when people say that "this in not classic, OS X can open as many apps as you want". You probably haven't stressed OS X VM to see that it is far from efficient. And please, let's stop with the fallacy that unused processes are swapped to HD. Every single opened process needs RAM, its usage can decrease if not active, but SOME memory is always needed. Just open Activity Monitor and click in "real memory", if you can find a process that uses 0 kb of RAM let me know. There is no magic even in the most in modern memory management system ( not OS X's case )



[ Reply to This | # ]
10.4: How to disable (and enable) Dashboard
Authored by: danieleran on Jul 30, '05 11:24:17PM

I wasn't making a technical argument about how VM works, but rather noting that in practical use, apps that are not active are not consuming RAM in the manner of Classic Mac OS.

In OS 9, if you have an app open, it got a minimum allocation of RAM that was lost to the system, and potentially took more. You had to close apps to open others or you ran out of memory.

Under OS X, you can have lots of applications open and apps that are not active will not be taking up a significant allocation of available RAM. Certainly, the more RAM you have, the better, and trying to run more than machine can handle will result in poor performance.

None of that changes the fact that, even you are trying to get by on minimal RAM, stopping Dashboard will not make a difference in system performance.



[ Reply to This | # ]
10.4: How to disable (and enable) Dashboard
Authored by: tceylan on Dec 11, '05 06:47:12PM

This is not correct. Please add 3-5 widgets to your dashboard, and lauch
"top" tool, and take a look at 'resident' memory usage. Typically my
widgets use about 2-5 megs each. I have seen some widgets use
as much as 30-50 megs. Rouge widgets might also continue
consuming CPU even if you don't run the dashboard. (I used to have
a map quest widget that used 30% of CPU after I put dashboard
in the foreground once, and minimized after).

So, disabling dashboard should make a difference in the performance depending
on other applications, and how much ram/cpu you have, and how much
physical ram is left. This difference might be insignificant if you have
a lot of free ram.

2-5 megs per widget might not be a significant amount of
RAM in most cases. However, claiming that dashboard does not
use any resources is not correct. I would probably rephrase this as
"dashboard uses resources as efficiently as possible."



[ Reply to This | # ]