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?

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.

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?

I was actually thinking along the OP's thoughts - startup is unbearably slow, and long play sessions would result in alt-tab going from "smooth" to "suck".

I was digging around doing voodoo that probably has no effect when I was going through SavedVars\ and... in a directory where most files are ~10kb (and that's rounding up.. a *lot*), SW_Stats has a 1.6 megabyte saved variable lua. Now, it's true that file size, performance, and runtime memory usage aren't necessarily correlated - a very small addon with no saved variables can easily just go through every byte of memory tossing a "1" in there, for example - but I gotta think that's a MASSIVE contributor.

Turned that off, and I guess the followup question is - does anyone have a sleek, minimalist damage meter addon that ONLY tracks a handful of stats (damage, and healing in any combination of raw, over, real) for party (raid) members ONLY? Reading through the LUA, I understand that there's simply no way to keep the level of information and meaningfully compact it, so I'm happy to lose information. I don't care if someone shadowbolted 10 times anymore versus incinerated, or what. The event parsing in combat is not a slowdown. It's startup, and accumulation.

I also think the difference with Pitbull's frame recycling vs. agUF has gotten rid of my "alt tabbing after a long play session" issue.

Also, has the verdict changed on using !!!StandAloneLibs or not?

MinnaStats.

It has a cute picture of a dog, but other than that its pretty minimalist and anecdotally I'm willing to say I couldn't notice it causing me any extra slowdown when I added it to my addons list.

The overall 'hit' to your performance between using PitBull and agUF is probably so insignificant (especially if you're not using the raid frames) that it's not something I doubt very many would notice. Although it's written with performance in mind, there is probably a point where the same amount of frames are in use by both addons, especially in long sessions without a relog or reloadui. Just something to keep in mind.

Also, if you want to keep with the "Ace2" tradition, Violation is the lightweight minimal data equivalent of DamageMeters. It does, however, require that each user have it running for their data to be tracked.

I'm a big fan of warmup + KLHP when I need to figure out which mod is causing a specific issue. 2.1 should be a huge boon, though. Maybe I can finally get my girlfriends computer to stop grinding to a halt. I think, though, that her problem is with video drivers. The NVidia control panel errors when I try to run it; clean install or no. I should see if I can get a her a good copy of XP, that might help,...

If I was unclear, then my apologies. I'm talking about grotesquely long play sessions that are definately edge case (although combinations of circumstances can speed this up to merely "profanely" long play sessions). Reloadui doesn't seem to clean up, though - a relog does. My voodoo explanation being that something is being allocated, tucked away, and never properly cleaned up.

In everyday usage, I don't think anyone would notice either. But I did, and it was either that, or SW_Stats, so.

That does sound like what I want (Player=damage, done!), with the small exception of everyone having to have it. I'm going to give Minnastats a try. At this point, I'm not interested in micromanaging or dissecting or anything. I just want to know, "Hey, $pug_warlock is doing less damage then my lacerate spam. FIRED."

Setting your max UI memory to 0 and running /script collectgarbage("setpause", 110) after every login will give you GC fairly close to how it'll be done in 2.1. The main cause of GC-related freezes now is having the UI max memory under twice as high as the initial memory, resulting in the incremental GC threshold never being hit.

Hm, that might actually help her out. Initially I was referring to the per-addon usage statistic that we'll have available, but this is good info. I knew about setting UI mem to 0, but hadn't considered how it might be related to the performance issues. Thanks

You'd be surprised. Data from tonight's raid: KTM spend 2.0% of it's processor time parsing combat log events. As long as you don't make any algorithmic blunders, you could easily parse 1000 combat long strings a second without noticing a change in performance, which is far more than is needed.

May I ask how you measured this? I'd like to see what numbers I get over here