Posted 08 April 2008 - 01:26 PM
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.
Addons I've tried include:
* KLHPerformanceMonitor - KLHPerformanceMonitor | World of Warcraft Addons | World of Warcraft @ Curse.com
* PerformanceFu - WAU
Addons on the TODO list are:
* AddonSpamFu - WAU
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.
Posted 08 April 2008 - 01:30 PM
Posted 08 April 2008 - 01:42 PM
Posted 08 April 2008 - 03:37 PM
Biggest trouble makers for my FPS were BigWigs, Recount and Grid (not sure if it was Grid itself, might have been some module - deffo know that the Layout plugins for Grid caused some freezes though).
Posted 10 April 2008 - 08:22 AM
Posted 11 April 2008 - 10:47 AM
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.
Posted 11 April 2008 - 11:47 AM
But yeah. Prat is one of those addons that seem to really spike whenever a lot happens at once. Chatterbox on my TODO list.
Posted 11 April 2008 - 06:42 PM
Posted 11 April 2008 - 10:09 PM
I set up a test last night with Prat fully embedded as my only Ace2 addon, and Chatterbox fully embedded as my only Ace3 addon.
The numbers kinda speak for themselves.
I also renamed Chatterbox to Chatter to solve a naming conflict, as a side note.
Posted 12 April 2008 - 04:10 AM
Posted 12 April 2008 - 05:50 AM
Posted 14 April 2008 - 08:18 PM
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.
Posted 14 April 2008 - 08:33 PM
- 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.
Posted 14 April 2008 - 09:20 PM
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!
Posted 14 April 2008 - 11:16 PM
Posted 15 April 2008 - 05:44 AM
Posted 15 April 2008 - 07:58 AM
Chatter is a great success! Prat is gone.
Posted 15 April 2008 - 08:15 AM
It can copy text fine, it just takes the whole content of the chatframe, or so it seems, which at times just is too much and you then need to track the one line you wanted to really copy that one out.
Posted 15 April 2008 - 06:21 PM
Anyhow, for a more general performance issue question - if we're running Ace with standalone libs (no embeds), is the info in OptionHouse accurate or does shared code still get accounted to the first addon that uses that lib?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users