Heavy CPU load

Andanor · 10-21-10, 07:55 AM

I'm having some strange behavior which causes heavy CPU load (tested with Addon Profiler) as soon as my raidframes show up.

It seems that every update function which is registered to raid frames fires up multiple times each second even if the related event has not been triggered (like ricons or aura for instance).

Anybody an idea where this may come from?
Thx in advance!

yj589794 · 10-21-10, 08:01 AM

Have you set .frequentupdates at a small interval on multiple elements/tags?

Posting you code would mean we wouldn't have to guess....

Andanor · 10-21-10, 08:24 AM

No .frequentUpdates used at all.

I've also tested this behavior with various other layouts...same thing there. Headers get updated multiple times per second even if the related event has not been fired.

yj589794 · 10-21-10, 08:30 AM

Originally Posted by Andanor

Headers get updated multiple times per second

This is a known bug that is caused by Blizzards code. It is the same reason why

portraits on headers flicker and constantly restart
clicks on header units sometimes get lost
other weird stuff happens

Just sit back and wait for Blizzard to fix it.

Andanor · 10-27-10, 04:34 AM

Just curious: Why does this header update bug does not affect other unit frames like Grid or SUF?

haste · 10-27-10, 05:37 AM

Originally Posted by Andanor

Just curious: Why does this header update bug does not affect other unit frames like Grid or SUF?

oUF runs full updates on :OnShow(), which is why it gets bitten by this. I've been thinking about reworking this, but haven't decided how yet, or if it's worth it.

I can't answer your question about other unit frames as I don't know their internals.

therealspanner · 11-01-10, 03:00 AM

Originally Posted by haste

oUF runs full updates on :OnShow(), which is why it gets bitten by this. I've been thinking about reworking this, but haven't decided how yet, or if it's worth it.

I can't answer your question about other unit frames as I don't know their internals.

SUF does it by caching the unit's guid and only running a full update if the guid changes. I did a quick and dirty test (used AddOn Profiler for 5 minutes in AV/WG) and it makes a big difference:

http://img822.imageshack.us/img822/1248/oufperftest.jpg

Top part is standard oUF, bottom is with very basic guid caching.

haste · 11-01-10, 06:35 AM

I'm honestly not sure if it's worth the effort to fix. The only reason it currently is an issue is because of the bug in the secure group header, and that should be fixed in 4.0.3, which shouldn't be too far from now.

Changing the OnShow to use the GUID would also mean that we need to implement more unit specific force updates. Currently oUF only had like two (target and mouseover).

The CPU cycles saved would probably not be to high after the bug is fixed as well.

(sent from my phone)