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: aranor on Jul 30, '05 12:23:52AM

60MB? What are you looking at? Real memory during normal use of Dashboard widgets for me is on average 3 or 4 MB per widget. That's barely anything. And the virtual memory listing doesn't matter.

And as for CPU, Dashboard does in fact go to sleep when it's not being shown. However, it's an optional thing - widgets are simply told to go to sleep, they're not actually forced to. But very rarely should you find a widget that actually needs to run when it's supposed to be asleep, and so if you are finding widgets that aren't sleeping when they should, that's just a poorly designed widget, and Dashboard can't be blamed for it.

So basically, Dashboard widgets take up barely any memory, and that's generally paged out of RAM when you leave Dashboard idle (that's why leaving Dashboard idle for a while makes it take a few seconds when you bring it back for it to start functioning - it has to page RAM back in for all the widgets you're using. And it uses no CPU. Konfabulator, on the other hand, last time I checked it used CPU constantly even with no widgets open, and it uses a *lot* more RAM than Dashboard does. I bought Konfabulator when it first came out, and a month later I had taken it out of my auto-startup and never looked back. That's because of the resource drain and the fact that I never found any widgets worth using. However, with Dashboard, while I use it infrequently, I do use widgets. Right now, I have 10 widgets running, and I don't mind. Their RAM usage is small, generally paged out to VM, and they use no CPU at all when not active.

I'd also like to point out, to the author of this article, that your comment "In my case, I just don't use it, and dislike having applications running that I don't use or need" just shows that you don't understand Dashboard. If you have no widgets open, you aren't running any extra applications. The Dashboard is built into the Dock - the only extra applications are the DashboardClient processes which manage individual widgets. So if you have no widgets open, you have no DashboardClient processes, and thus no extra applications. I'd be surprised if the terminal command did anything other than simply tell the Dock "don't let me bring forward the Dashboard layer".



[ Reply to This | # ]
10.4: How to disable (and enable) Dashboard
Authored by: terabolic_radius on Apr 08, '06 08:12:46AM

aranor,

i don't understand why you say that an unused widget doesn't use RAM. i am running 10.4.5 on a 2001 iBook w/ 384 MB of RAM, and using the Activity Monitor, it shows quite distinctly that I have a widget using 114+ MB (real mem, not VM)! and 20% of CPU, oscillating b/w 1% & 20%! and i have not called up the dashboard in the past hour either. and the other widgets i have active when using the dashboard all use about 10MB and their memory usage is listed under the 'Real' column of the Activity Monitor.

out of 384MB of total physical RAM, the Activity Monitor says i am using 373.90MB and i am only running Safari, the Activity Monitor, the Finder of course, and DockFun (which only consumes 12MB). the rest of the ram is eaten up by Dashboard and the widgets, again according to the Activity Monitor.

but if i am missing sth, so please tell me.



[ Reply to This | # ]