Originally Posted by Duugu
This mod was originally to show that the client's performance isn't affected by the mod's memory usage but only by the mod's activity.
|
That's quite interesting in itself...
With O.B.I., I'd got myself into a position where I had 2 mechanisms for updating ActionButtons.
One method was entirely event-based and used minimal CPU - but it reset (e.g. discarded) tables a LOT (hence he original issue here) and so it's memory usage was constantly climbing (until GC lowered it and it started again). This approach had some issues with the way some actionbar addons worked which were going to be hard to solve too.
The approach I've switched to now is more cpu intensive BUT it's very memory-efficient in that it uses no more memory once initially loaded. It also uses less CPU when you're in-combat which I think is where it matters most
What you're saying tho is that I've made my addon worse in performance terms??
