Benchmarking Addons?

mad-doc · 05/30/07, 10:43 AM

I am looking for an addon, that allows me to find out how much addons directly affect my framerate.
Is there any way to do this? It looks like you dont have anything to run a benchmark, so this might be a problem. I am trying to get higher fps because i want to run fraps again but this wont work in arenas with 10 fps

.
Perhaps someone else allready has done this and can post his findings.

And a little bit offtopic but still has something to do with it, is there a guide concerning general fps improvment for wow, like the cfg guides for the quake series, cs, ut.

Ossy · 05/30/07, 12:36 PM

You can run Protractor to find out the Memusage and CPU time of your addons. That's the only similar addon I can think of right now.

Apate · 05/30/07, 12:39 PM

Check out Fubar_Usage also

Cryect · 05/31/07, 1:23 AM

As well there is also PerformanceFu.

There is also one incorporated in some development addon I can't think of the name but I doubt its what you want.

Demi9OD · 06/01/07, 4:49 AM

Is this a normal looking shot for Standalone libraries? I just recently switched from "with externals" to standalone libs and while performance has gone up, I am curious as to what "Ace2" is handling and why it is required. I was always under the impression that only the libs mattered and the actual Ace2 addon was for developers only.

Caldar · 06/01/07, 8:45 AM

Ace2 includes AceAddon, AceComm, AceConsole, AceDB, AceDebug, AceEvent, AceHook, AceLibrary, AceLocale, AceModuleCore, AceOO, and AceTab.

It is the heart of the Ace addons you are running and some part of it ends up being used by most every Ace addon. I would say that the numbers listed for it are fine.

Cel · 06/01/07, 9:11 AM

I used protractor to take a look at my CPU usage and something ~55% of it is Ace... which doesn't tell me a whole lot. How can I tell which Ace addon is making heavy use of the libraries, and thus slowing my FPS down?

Cryect · 06/01/07, 12:46 PM

Originally Posted by Cel

I used protractor to take a look at my CPU usage and something ~55% of it is Ace... which doesn't tell me a whole lot. How can I tell which Ace addon is making heavy use of the libraries, and thus slowing my FPS down?

Unfortunately you can't which kinda sucks.

Shadowed · 06/01/07, 12:50 PM

The only way you can really test how much an addon is using including libraries, is disable all addons except for the one you're testing.

Cryect · 06/01/07, 1:00 PM

Unfortunately, thats not even accurate since a lot of the libraries will often process something once then send it to many different addons (example if you are using SCT, Recount, Omen, Simple Combat Log, and Eavesdrop they all get their data from Parser-1.1 which parses the combat log messages only once).

Though does give you a rough idea and a lot of libraries are there to try to make things easier for the developer and not really help spread out performance usage.

Antiarc · 06/01/07, 1:13 PM

Originally Posted by Cel

I used protractor to take a look at my CPU usage and something ~55% of it is Ace... which doesn't tell me a whole lot. How can I tell which Ace addon is making heavy use of the libraries, and thus slowing my FPS down?

You can profile the _G table, which should give you a list of functions by CPU usage. I find that handy in tracking down sore spots...sometimes.

You can also profile individual addons by looking up their master table name and plugging that in. It can be quite useful.

Shadowed · 06/01/07, 1:14 PM

Originally Posted by Cryect

Unfortunately, thats not even accurate since a lot of the libraries will often process something once then send it to many different addons (example if you are using SCT, Recount, Omen, Simple Combat Log, and Eavesdrop they all get their data from Parser-1.1 which parses the combat log messages only once).

Though does give you a rough idea and a lot of libraries are there to try to make things easier for the developer and not really help spread out performance usage.

Indeed, but it gives you a far better number then trying to guess which one is caused by a library and which isn't.

Demi9OD · 06/01/07, 5:06 PM

Would it stand to reason then to run embedded libraries rather than shared simply for the sake of testing? Once you find any hogs you can toss them out, kill all your lib folders and re download standalone libs. Or would this skew our results somehow?

• Shalas · 06/01/07, 6:43 PM

Originally Posted by Demi9OD

Would it stand to reason then to run embedded libraries rather than shared simply for the sake of testing? Once you find any hogs you can toss them out, kill all your lib folders and re download standalone libs. Or would this skew our results somehow?

Even with embedded libs only one copy of each library is actually loaded. I suppose you could mangle all of the library names so that each addon gets its own copy, but it'd be a decent amount of work.

Demi9OD · 06/03/07, 4:51 AM

Originally Posted by Antiarc

You can profile the _G table, which should give you a list of functions by CPU usage. I find that handy in tracking down sore spots...sometimes.

You can also profile individual addons by looking up their master table name and plugging that in. It can be quite useful.

How are these accomplished?