After 2.4 my addon addiction has started to become a real problem. In 2.3 I had lag and FPS issues during only a handful of heavy nuke fights, like RoS. Since 2.4 I can get spikes which completely locks up my UI for up to several seconds. To get to the bottom of this, I have been looking for profiling tools and the likes to try to get some clue as to why I get these. I've tried searching for relevant information in this sub-forum, but alas, no luck. Therefore I figured a new thread wouldn't hurt.
Short lists, I know, but these seem to be the best I've run into so far. My attempts to solve the situation have been to reinstall addons(in case old files/libs were loaded), disable a ton of "oh! shiny!" stuff that I don't really need and go over modules in addons like PitBull. Nothing of this has solved anything. Spikes are still there.
Then to the question: What addons and strategies do you use to sort your addon woes? And try to keep the "default UI FTWWWww!1" spam as low as possible, thanks.
I fired up AddonSpam_Fu yesterday. Nothing revolutionary, but I did notice three guildies running SW_Stats and sending large chunks of data. Not that many packages, but they were much larger than most. Anyone remember what the old issue with spamming the addon channel was? Was it the number of packages sent or the actual size that dragged fellow raiders down?
I've been using OptionHouse lately. It works well enough.
Tangentally, I've been tearing apart my mods to figure out how much code is being disguised in libraries. Turns out that Prat was eating my framerate alive, so I wrote Chatterbox to do the same thing. Dropped my reported Ace2 CPU time usage from about 13-14ms/1 sec to about 6ms/1 sec. Can't complain about that.
Does Prat eat that much even with 1/2 it's modules disabled? I've always liked Prat for the functionality but if it's screwing my game play and there's something better I'd deffinately try it. I too have been having bouts of lag and occasional freezes. Also, the incredibly annoying moment of lag upon entering or leaving combat.
We've had serious problems since 2.4 with grid in our guild, so I'd suggest making sure it's disabled as a first step. Beyond that, I haven't seen any tools more useful than PerformanceFu, so if you do, I'd be interested in hearing your experiences-
If you're a developer type, Expo is a great tool for profiling. You can give it a table (most Ace addons are in a table, for example) and it'll measure CPU and memory usage per function. It's a great tool for tracking down which parts of an addon are slow, which can help you decide which modules to disable or whatnot.
I hope I am not hjacking your thread but I think it would be interesting to find out which of the commonly used Addons are (performance wise) not the best and to help interpret the values from the addons you posted (performance_fu, optionhouse, ...)
I tested using Optionhouse, I reinstalled all my Addons using embedded libraries:
As you can see Baggins and Pitbull take up the most CPU time. I took this screenshot after about five minutes of idling in Shattrath. And I have no problems with Grid whatsoever.
My problem now is that I don't really know what these values mean. Are 2.7/2.8 reasonable values for CPU/sec for an inventory addon and unitframes? My first thought was that Baggins shouldn't take up any CPU time when doing nothing.
I then proceeded to delete all my addons and installed Baggins not embedding the libraries. Here is a screenshot of Baggins installed this way and this is a screenshot of PitBull.
For Baggins it is Ace2 which takes up most of the CPU time and for PitBull LibDogTag uses almost all of its CPU time. Again: I don't know if a value of 2.2 vor CPU/sec is normal or if I should start to look for another unit frame addon.
So if anyone could share some insight it would be greatly appreciated.
- Baggins is likely being blamed for all of your Ace2 libraries' CPU and RAM usage, as its the first of your Ace2 mods to load, alphabetically (this is due to running embedded libraries)
- Chinchilla is your first Rock mod, so it inherits the shared Rock CPU/RAM. PitBull-3.0 suffers because of LibDogTag-3.0, which has some pretty serious CPU consumption issues at the moment. ckknight is working on that though.
- Chatter is your first Ace3 mod, alphabetically, so again, it inherits all of the CPU/RAM blame for Ace3 on top of its own code.
The cpu/sec number is ms/sec. A value of 1000 means that 100% of all available computing time is being spent on that mod.
Those numbers are very decent, and are nothing to be worried about. I would recommend profiling in combat to get a more "real world" reading. Profiling while idling is a good way to find misbehaving addons, but it's good to remember that the time you care about framerate the most is in combat.
Thank you for your quick reply.
It will help me a lot in evaluating my addons (as I now understand the values and have a reference value to compare to). And I will try as you suggested and profile again in a combat.
And very good to hear about LibDogTags performance being worked on!
I recently reinstalled all Ace modules to not include externals. This helped me localize LibDogTag as the major sinner. It uses up to six times as much CPU cycles as the next on the list. I haven't looked through my addons and seen which import DogTags, but something seems amiss.