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

Click here to return to the 'enabled + disabled compared' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
enabled + disabled compared
Authored by: echo on Jul 29, '05 04:07:48PM

From Tiger's beginning, I had closed all widgets, dragged dashboard's icon out of the dock, disabled the fKey+ deleted associated prefs files + caches. In Activity Monitor I couldn't identify any dashboard processes running, but always wondered if there was any overhead from it.

I just compared info from Activity Monitor with dashboard enabled + disabled, both after fresh logins, and memory + cpu usage (+ other data) remains the same. I'm convinced disabling dashboard has no advantage.

[ Reply to This | # ]
enabled + disabled compared
Authored by: jasenko on Jul 29, '05 06:36:11PM

Even if you don't use any widgets, when you press F12, you can instantly see the change. That means that something is working in the background. I still didn't find out what process is that, but I believe that it is on kernel level.
Since disabling Dashboard few weeks ago, stability of the system improved dramatically so my theory that it runs directly from the kernel space got some credibility.

[ Reply to This | # ]
enabled + disabled compared
Authored by: burntout on Jul 31, '05 10:05:50AM

Yes, it's called If you view processes hierarchically in Activity Monitor you will see all widget processes are children of the Dock. If you don't have any widgets running, Dashboard will do nothing. Anything you think you detect is a placebo.

[ Reply to This | # ]
enabled + disabled compared
Authored by: ubi on Aug 01, '05 09:14:25PM
I think it does save some real RAM, even if you don't (accidentally) start Dashboard by hitting F12 or a hot corner. I made the following bash aliases for convenience:

alias dashoff='defaults write mcx-disabled -boolean YES ; \
sleep 2 ; killall Dock ; echo Dashboard disabled.'

alias dashon='defaults write mcx-disabled -boolean NO ; \
sleep 2 ; killall Dock ; echo Dashboard enabled.'

alias dashstat='if (( `defaults read mcx-disabled` )) ; \
then echo Dashboard is disabled. ; \
else echo Dashboard is enabled. ; fi'

I have 7 widgets running, with 112 of 640 MB RAM free. When I execute 'dashoff', I now have 153 MB free. After 'dashon', I have 151 MB free. So a couple of megs got eaten just now, even before hitting F12 to see the widgets.

[ Reply to This | # ]