Addon resource usage?
 

Anyone know if there is a way to see what addons are using more/the most resources? I recently had to disable addons to fix a bugged login, and the difference in performance upon logging in was astounding. I really wasn't used to it, and now that i have had a taste I want more!

Warmup

found on files.wowace.com

The profiling options right now are pretty weak. It's mostly comparing an addon running to that addon not running. The proliferation of Ace addons makes it more difficult, as 15 different addons might be abusing the same line of code in one library loaded separately.

In 2.1, there will be much more extensive profiling options for both memory (enabled by default) and cpu (disabled by default) usage by individual addons. I'll be doing a complete overview of my addons when I get the time in the post 2.1 world; for now, I'll just accept that my loading time (but nothing else, really) is slower than it should be.

Is the load time directly proportional to in-game resource usage?

I would guestimate no. There are mods that don't have 'huge' startup time/mem-usage but accelerates insanely much due to syncing/parsing addonmsgs/data arrays etc. A good example would be SW Stats that isnt to bad at start but can eat tons of mem/resources thanks to msg parsing and data stored.

Running on a crappy comp I've isolated most of my lag/performance issues to addons/settings that stores data or parses addonmsgs/syncs.

Mods used:
Ace2
ag_UnitFrames
AltClicktoAddItem
Atlas
Atlasloot
Automaton
Bartender 3
cgCrafty
Clearfont2
Cosplay
Cryolysis
DeadlyBossMods
Damage Meters
Deuce Commander
ElkBuffBar
Errormonster
Grid
Itemrack
KLHThreatmeter
MobHealth
OminousCastingBar
Rating Buster
sct
SimpleCombatLog
simpleMinimap
Skinner
XLoot



Any idea which ones would cause the most load then?

Get KLHPerformanceMeter for ingame actual performance. Warmup is only good for determining load time stuff which still makes it useful.

Actually you'll have to grab it off Curse. It was never released directly on WoWAce because of having to be loaded first (with the !! pre-cursor) or something like that.

Unsure, but here are a few comments on the stuff I recognized. With Warmup you can determine your total mem-usage and set your memory accordingly. Might also be usefull getting a mod like PerformanceFu (what I use) to force garbage dumps.



Atlas & Atlastloot - Was a long time since I used these, but as far as I remember the loot and map occupies some mem with its database. It should be static so it won't increase during gameplay.


DeadlyBossMods - I'm yet to discover an encounter in TBC where this mod actually is needed... but thats my personal view tho :>


Damage Meters - If it syncs thru a addonchannel it can eat performance during raids etc. I'm using the mod-version of Recap to see if that is less consuming. I've used SW Stats before and I just can't run it due to its excessive mem/cpu use.


Deuce Commander - Seems like a heap of junk. I don't like mod-packages like these because it usually means getting mods you don't really need. I would recommend removing it and if a need for a certain mod arises - find a single one that solves your task. Might take you a good time extra - but gives you increased control.


KLHThreatmeter - Never used this mod, but from what I have read it dishes out alot of msg's thru the addonchannel. Inconjuction with perhaps another mod that sends addonmsgs this might give alot of data to parse during raids.


XLoot - Had it once, sure it looks good but doesn't really do anything that I couldn't handle with original UI. Just takes mem.

Dukes: True! It was on wowace before, but I now see that it isn't any longer.

KLHPerformanceMeter or TekSupport can give you estimations of runtime and memory usage for mods.

When 2.1 hits, profiling is going to be supported in the UI to a much greater extent.

What Praanz said is pretty much correct, just because it takes an extra 10-30 seconds to load into the game doesn't mean that you're going to be taking a performance hit during your entire play, it shouldn't really effect zone loading (of course depending on the mods) that much since everythings already been loaded when you first logged in.

If you like an addon you should use it and not worry about performance that much unless you're really noticing an effect on game play, and also remember that just because it's an Ace2 mod doesn't mean it's better.

DC simply converts slash commands of all running ace2 mods into a FuBar dewdrop menu. It's just a configuration tool.

My guess would be that KLHThreatmeter and Damage Meters have the greatest impact on FPS during raid encounters.
This is due to sending a lot of local events (e.g. your damage/healing done) and parsing remote events (e.g. your raids damage/healing).

May I ask what you're trying to do?
Improving your performance could be achieved by
- toning down your graphic details and especially "Terrain Distance"
- stopping any other processes besides WoW (browser, ICQ and whatnot)

You should also always update your addons to the latest versions; e.g. GridStatusHots was a real CPU killer a couple of versions ago.

Please don't write stuff like that. No offense intended, but you could at least try to find out what it really does before you give such an uninformed statement.
As Miaxi already said, DeuceCommander is a graphical interface to the slash commands of Ace mods. It surely does not take up lots of memory or performance.
If you're really concerned you can disable it when you're done configuring your addons.

If you use alot of ace mods you need to realize they are largely "beta" mods in constant development. Quality varies alot even for the same mod week to week. You can also gain back some loading time by downloading them all without externals and using the standalone libraries.

All of these parse alot of data and will cause slow downs on a slower computer:

SimpleCombatLog
DamageMeter
KTMThreatMeter
DeadlyBossMods

Do you really need them?