[naashraf]

I noticed that while Dashboard is active on the screen the CPU Memory usage hits the highest level.Captured screen is below. Do you see the same increase in the CPU memory usage? I have used Konfabulator before but the memory usage was not this much. Not sure but I think this Dashboard memory consumption is gonna reduce the battery life. Correct me if I am wrong.

[Paul]

It could be because you have a shitload of them open (or one of them has a memory leak...)

[ast3r3x]

This is why you can't give people choice. They put 7 clocks at the bottom of their screen and pretend like it's necessary. Than they wonder why it pegs their CPU to be running javascripts CONSTANTLY to control them all.

I also despise that Apple has a game in their dashboard as default. That shouldn't be a widget. That should be a stand alone application.

People have widgets out just for the sake of having them visible. It's driving me crazy already, and they have POINTLESS ones that count the number of days until new years?! WTF is that?!

I'm sorry, but I am going to have an aneurism because people can't control themselves. They are like my grandpa who goes to the dollar store and buys 12 portable FM radios which have no purpose other than they are $.99

</rant>

naashraf, nothing personal, almost everyone is doing this type of thing.

[Brad]

Originally Posted by ast3r3x CONSISTENTLY

I would expect them to be consistent if I have two or twenty. I think you mean CONSTANTLY.

[ast3r3x]

Originally Posted by Brad I would expect them to be consistent if I have two or twenty. I think you mean CONSTANTLY.

*fixed*

1) Never correct a rant
2) Damn spell check.
3) Damn me not checking what I picked from the spell check option.
4) Damn my inaccurate typing during rants.
5) Damn the man.

[naashraf]

Nah......I know it is not personal.......You know it is new so people get excited.....You are right there was no point having 7 clocks and other widgets perhaps i will never use. Now I have reduced the number of widgets, or clocks as I had them too many, and the CPU usage is less then half now

[ast3r3x]

Originally Posted by naashraf Nah......I know it is not personal.......You know it is new so people get excited.....You are right there was no point having 7 clocks and other widgets perhaps i will never used. Now I have reduced the number of widgets, or clocks as I had them too many, and the CPU usage is less then half now

Well I have to admit after my post, I was desperately hoping that was the culprit, or I'd look like even more of an ass

[naashraf]

Well, I admit I was using only one clock and then I read this post and noticed the first image on the post shows a desktop with 7 clocks and every other widget so far released and I thought "Why Not" and went for it. Perhaps that guy does not know how much CPU memeory is being used.

[Kickaha]

I've just gotta ask.

nashraaf, how much memory does your CPU have?

[naashraf]

I know, I know what is your point here

[BarracksSi]

I wouldn't be too worried -- after all, what else are you going to be doing when Dashboard is up?

[Kickaha]

Thought this would be of interest: (From an Apple dev over at slashdot)

Is there a way to make Dashboard widgets sticky on the desktop? You don't want them to. One of the benefits of the Dashboard layer is the fact that when the Dashboard isn't visible, the widgets are completely suspended, consuming no CPU cycles at all. If you put a widget on the screen outside the Dasboard layer --which of course you can do, if you run Dashboard in debug mode --it'll execute its run loop all the time, sucking up CPU cycles unnecessarily.

[Paul]

http://www.macosxhints.com/article.p...50422172929402
has the hint to run Dashboard in debug mode...

Wait, so that means effectively dashboard is ALWAYS "active" and even the widgets that are not visible would still be updating?

Bummer...

[chucker]

Originally Posted by Paul http://www.macosxhints.com/article.p...50422172929402 has the hint to run Dashboard in debug mode... Wait, so that means effectively dashboard is ALWAYS "active" and even the widgets that are not visible would still be updating? Bummer...

When the Dashboard gets hidden, the onHide event gets sent to all widgets. They have to implement a manual means of not updating -- most do this just by the code of onHide(sleep(), effectively "going to sleep" while the Dashboard isn't visible. Once the Dashboard reappears, they get sent another event and then continue.

They can, of course, opt not to "sleep" at all, which can in certain situations be useful.