Tracking down UI lag - Page 2

• Snowy · 05/25/07, 12:42 AM

When did they take out the box at the character login screen where you could allocate the amount of memory to addons? Was that just this patch? Maybe if it's being done dynamically it's being done poorly with some systems now. I remember I'd hit terrible FPS when I got close to the limit, and it feels to a lesser degree like that now.

Arnath · 05/25/07, 1:08 AM

Originally Posted by Axen

I had massive memory usage and terrible FPS after upgrading my Ace2 mods. I disabled everything but a few essential AddOns and saw no improvement. I thought it was the new ag_UnitFrames, but it turned out to be SWStats. Nuking the data fixed the problem, but I watched my memory usage steadily increase even after the data was erased. Totally disabling SWStats fixed all of my UI lag.

Is it just me or does SWStats seem to be causing more lag than usual this patch? Granted I never checked how much memory it was taking beforehand but when I have it enabled now it takes something like 6 megs which is a good 3 times more than any other mod I have.

Asmo · 05/25/07, 2:24 AM

Originally Posted by Theras

Does anybody else's FuBar seem to use an absurd amount of memory and CPU time? Mine is currently using double the CPU time as my ag UnitFrames does, and is using about triple the amount of memory.

Edit: it occurs to me that the FuBar plugin I'm using to track performance data could be the culprit, but wouldn't that track under the individual plugin, and not FuBar itself?

Yep I checked out the profiling for the first time today with PerformanceFU. And after changing it to see the top 20 and using it a bit while grinding it looked roughly something like:

KTM 200s
Fubar 130s
Addon nr 3 40s
and down from there

PerformanceFU was listed separately in there but don't remember how much that used, wasn't anything special. So yeah fubar using 3-4x the cputime of my other addons (with the exception of KTM) seems pretty off to me too. It was also by far using the most memory.

• Chicken · 05/25/07, 5:47 AM

Originally Posted by Theras

Does anybody else's FuBar seem to use an absurd amount of memory and CPU time? Mine is currently using double the CPU time as my ag UnitFrames does, and is using about triple the amount of memory.

Edit: it occurs to me that the FuBar plugin I'm using to track performance data could be the culprit, but wouldn't that track under the individual plugin, and not FuBar itself?

Are you using embedded libraries or not? If you are it's likely that all of the resources used by the FuBarPlugin library are being attributed to FuBar itself.

I can't say I've noticed FuBar taking up a lot of performance, and if you're not using embedded libraries than I'm mystified.

PerformanceFu did jump very high for me when I had CPU Profiling enabled I might add.

Apate · 05/25/07, 10:32 AM

Originally Posted by Ragnor

Quick way to test that would to get a stand alone mod to list performance, anyone recommend a good one?

FuBar_Usage

Kalman · 05/25/07, 10:50 AM

Originally Posted by Snowy

When did they take out the box at the character login screen where you could allocate the amount of memory to addons? Was that just this patch? Maybe if it's being done dynamically it's being done poorly with some systems now. I remember I'd hit terrible FPS when I got close to the limit, and it feels to a lesser degree like that now.

They changed the way garbage collection is being done (incrementally as opposed to a full collection), so there's no longer a UI memory limit as of this patch.

From the UI notes for 2.1: "# The script memory manager has been optimized and the garbage collection tuned so there is no longer any need for a hard cap on the amount of UI memory available."

• Shalas · 05/25/07, 11:08 AM

Originally Posted by Snowy

When did they take out the box at the character login screen where you could allocate the amount of memory to addons? Was that just this patch? Maybe if it's being done dynamically it's being done poorly with some systems now. I remember I'd hit terrible FPS when I got close to the limit, and it feels to a lesser degree like that now.

That was removed in 2.1 due to that it really didn't do anything useful, and if set too low it could cause significant performance problems (by forcing GCs at bad times).