http://www.darcynorman.net/2005/05/05/dashboard-widgets-can-be-cpu-aggressive/ just a lowly edtech geek, mumble mumble university of calgary Mon, 15 Mar 2010 22:04:56 -0600 http://wordpress.org/?v=2.9.2 hourly 1 http://www.darcynorman.net/2005/05/05/dashboard-widgets-can-be-cpu-aggressive/#comment-79845 Doug Davis Wed, 31 Dec 1969 17:00:00 +0000 #comment-79845 I just found this out after an upgrade .. what a collossal waste of cpu .. I guess they count the microseconds in a for loop or something I just found this out after an upgrade .. what a collossal waste of cpu .. I guess they count the microseconds in a for loop or something

]]> http://www.darcynorman.net/2005/05/05/dashboard-widgets-can-be-cpu-aggressive/#comment-79846 Nikos Wed, 31 Dec 1969 17:00:00 +0000 #comment-79846 I was shocked to notice that as well - thats why i switched to another clock widget which spends only.. 15% of the cpu instead of 20 ;-) I was shocked to notice that as well – thats why i switched to another clock widget which spends only.. 15% of the cpu instead of 20

]]> http://www.darcynorman.net/2005/05/05/dashboard-widgets-can-be-cpu-aggressive/#comment-79847 Michael Salsbury Wed, 31 Dec 1969 17:00:00 +0000 #comment-79847 The situation gets worse the longer World Clock is left up and running. I left a single instance going for about 2 weeks and found it had eaten 46% of the CPU. I'm currently conducting a more scientific experiment, taking performance snapshots every hour using a cron task and the "ps" command to snapshot all the active widgets. What I'm finding is World Clock eats an additional 1% of CPU each hour it's active and more RAM as well. I'm trying to leave the Dashboard up and running on the system as long as possible, in the hope of accumulating enough performance data to convince Apple that they've got a real problem in that widget since people really like to use it they generally can't afford to lose 46% of their CPU... See the latest data at http://mikesalsbury.com/mambo/content/view/238/1/ The situation gets worse the longer World Clock is left up and running. I left a single instance going for about 2 weeks and found it had eaten 46% of the CPU. I’m currently conducting a more scientific experiment, taking performance snapshots every hour using a cron task and the “ps” command to snapshot all the active widgets. What I’m finding is World Clock eats an additional 1% of CPU each hour it’s active and more RAM as well. I’m trying to leave the Dashboard up and running on the system as long as possible, in the hope of accumulating enough performance data to convince Apple that they’ve got a real problem in that widget since people really like to use it they generally can’t afford to lose 46% of their CPU… See the latest data at http://mikesalsbury.com/mambo/content/view/238/1/

]]>