My interface lags for a second or so every time someone joins/leaves the party/raid or zones in or out. I suspect this has to do with XPerl's raid functionality (after trying to research some on the topic). Verifying that has been problematic, since it seems to be a combination of mods that are causing it.

I'm curious if there is a method of finding out what calls are being made that are causing the UI lag. I keep things up to date, and try to keep my UI fairly consistent as far as mod makeup and layout goes. But I'd like to find a good way to debug problems like this (when they become problems). Does anyone have any suggestions on how to track this? Maybe there's some nice debug tool that you love?

There didn't seem to be a thread on actual UI debugging yet. If there was and I missed it feel free to lock/heap. Thanks.

I have brought this issue up awhile ago in this thread: Odd Raid...

I have managed to fix it by removing SavedVariables folder and let my mods rebuild it, after that I simply copied over my Gather.lua file and reconfigured all other addons.

That sounds painful. I'd really rather not reconfigure all my addons. There has got to be a better way to track WHICH SavedVariable is causing it and eliminate only that one.

I'll try cleaning the folder some tonight, I definitely don't have time this evening for a full UI rebuild though.

Oh, thanks. I will probably hold tight and wait then. It's only really annoying during raid formup with everyone joining/zoning in.

I think Niagra was doing it for me, very similar to Deuce Commander. If you have any addons that are like Ace2 control panels they seem to freak out every once in awhile.

Any addons that handle this out yet? I'd love to see individual cpu usage on Ace2 addons.

I think Fubar_Usage (from wowace.com/files) is what you're looking for. Shows cpu usage for each addon and has some sorting options. Was interesting to see KTM was #1 cpu using addon even while idling in Shattrath, with my unit frames (AG) coming second.

You can configure it to show up to 20, and it's also possible to enable CPU Profiling of addon usage as well (CPU Profiling is probably more key to figuring out performance bottleneck, than memory profiling is). The CPU Profiling is disabled by default because having it on will cause a performance hit, I recommend trying that out on some content that's trivial for you.

For example, my two largest memory consuming addons still consume relatively little CPU time, while KTM, which has a low memory footprint, takes up most of my CPU time, oddly enough even when I'm flying around doing nothing.

(Edit: Actually Ace2 is my largest memory consumer and cpu time consumer, but as I'm running stand-alone ace libraries and run ~60 Ace mods that's no wonder)

Using Protractor, I enabled CPU Profiling for a short while just to see (no combat at all), and yeah, KTM was scary bad. Even with my system it was causing a stutter every few seconds, though, so it's not a great thing to keep on.

Couldn't get any real combat testing going b/c my latency was through the roof due to other circumstances.

BTW, if you use script profiling to figure out whats wrong. Make sure you disable script profiling when you done since it has a pretty negative hit on performance.

Just do the below to disable it again.

/script SetCVar("scriptProfile","0")