|
|
enabled + disabled compared
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.
enabled + disabled compared
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.
enabled + disabled compared
Yes, it's called Dock.app. 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.
enabled + disabled compared
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:
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.
|
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|