ObjectDock eats 30-40% cpu

I love ObjectDock and I'd dearly like to have it replace my Windows taskbar. However, it is currently continuously eating a third of my CPU time, and that's just not acceptable.

I know my computer isn't the fastest anymore, but seriously, no "menu" program should be that resource intensive. Plus, I can't see how ObjectDock would need constant CPU time, even when I'm not using it (i.e. it's just there sitting at the bottom of my screen).

Can the steep CPU usage be remedied by tweaking ObjectDock? Or might it be some docklet I loaded that's eating all the CPU?

Currently, I'm using the clock, Andreas Verhoeven's calendar (version 3.4) and Start Menu docklet, and a system tray docklet, that I can't find the credits of right now. Plus, a bunch of shortcuts and the taskbar is enabled.

Any help would be greatly appreciated.

Grtz,
One
1,973 views 14 replies
Reply #1 Top
After posting this message I felt kinda stupid for not doing my own dirty work, so I experimented a little with removing docklets and, lo and behold, the systray docklet was the culprit. I guess it was continuously polling the regular systray or something.

But this sucks, since now I don't have a systray anymore, and you kinda need the thing in Windows. Does anybody know a good replacement for it?

Grtz,
One
Reply #2 Top
Object Bar... https://www.stardock.com/products/objectbar
Reply #3 Top
if you're using icons instead of png images, that will rob you of processing time also. i'm sure someone will have a remedy for you without having to go to a new program like objectbar
Reply #4 Top
You had a systray docklet?! Where did you get it?! Can I have a link.....PLEASE?!
Reply #5 Top
#4 by Skinner CerebroJD - 4/19/2004 10:24:52 AM
You had a systray docklet?! Where did you get it?! Can I have a link.....PLEASE?!


It was hidden pretty well. I had to go to the object dock library, key in "tray" for the search string and hit the search button. j/k (couldn't resist)

https://www.wincustomize.com/skins.asp?library=29&SkinID=3916

[Message Edited]
Reply #7 Top
Its new. That would be why I didnt see it. Cant get it to work though. OD crashes.
Reply #8 Top
if you're using icons instead of png images, that will rob you of processing time also.

I believe you have that backwards....   ICO is native to Windows, PNG must be rendered.



Powered by SkinBrowser!


[Message Edited]
Reply #9 Top
koasati i've always thought it was the other way around in rendering the image.. while ico is native to windows, its being used as an image within objectdock.. but not an image as easily manipulated as a png. it is not an icon in the sense of being used by the shell.

my toshiba satallite didnt have a whole lot of punch in its video, and running a dock full of icons was very sluggish and choppy whereas a dock full of png's was fast and smooth.
Reply #10 Top
My png dock is very fast. Never used icons on it tho.
Reply #12 Top
Personal choice.
Reply #13 Top
Arg. Apparently I stutter. Or at least click too fast.
[Message Edited]
Reply #14 Top
if it come down to performance his personal choice is which one is smoother..hehe.