Broker CPU / Memory / Performance 

//Edit: Fixed in r8//

you didn't seen the tooltip shortcut while cpu profiling was disabled ? its Ctrl - Alt - LeftClick on the broker icon, I will do something for it to be more visible, thank you for the feedback

let me know if that's a good idea or not, allowing viewing memory while CPU profiling is disabled, I don't really know if that option is worse to add since here I prefer having CPU stats and secondly memory rather than just showing at Memory while profiling disabled because memory usage doesn't really give an idea of the resource really used.

Feel free anyway to post anything you would like to have in the mod and then we'll see if that's worse adding as eitrax did.

ok thats is on ToDo list, will be in next revision with a few more useful options and few ommitted performance codes tweaks like sending few globals to locals

no probs you 'll appreciate I think next revision that adds some handy features, btw don't worry seeing mods using cpus they need all to but you should much care on the mods that have the highest requests times in cpu and finding a smallest alternative, for example take Pitbull4 and you will notice while AFK in a city it can have a 30% diff , in less than 60sec this mod told your CPU to work for 20sec, this is giant, and alternative would be to throw that crap mod and go for a mod that doesn't waste resource that much like StellarUF (Stuf)

Another funny Benchmark I did here is comparing Broker_CPU to PerformanceFu, the difference is giant aswell because while fully working, Broker_CPU can't reach PerformanceFu resource usage while this last is not told to work. In short by running PerformanceFu you are wasting lots of resources because it does useless job in the background, so far much than what is required to update a simple text in a fubar/ldb plugin ....

Thanks for your kind feedback

next revision > 9 will tell less work to QTip, actually it tells QTip to
recreate each lines to each update waves, I should rather create
the lines only once and just care at updating the cells to each update,
testing here, it seems QTip uses around 2x less cpus after applying this
tweak because the job it does when using QTip:Clear() is quite big when
called several times and very quickly, thats even bigger by listing more mods,
next revisions will focus on lighten QTip jobs I promise to have it near as
light as using GameTooltip (technicaly not really possible anyway it will
always use more cpus to use QTip than using GameTooltip because it has
to calculate cells sizes)

//edit; btw an idea popped up in same time writing i should note it to
not forget, I should add a few options to enable/disable the lib detection
so you can use GameTooltip for example even if LibQTip is detected so you
are not forced to disable the whole LibQTip if do you prefer the simple
gameTooltip method into the mod.

//edit: I will change the scale system too has it could change all
GameTooltip scales yet , I really hate that crap GameTooltip system ,
sooo boring -_-, I think I will remove it from changing GT so the ldb
displays only handles it and I just change QTip scales. thats easier

sure, I was waiting for someone to tell it I'm lazy adding options I don't need
I will also add an option to force the collect of the garbage memory and also
update the collection function so the mod will generate less garbage and so
on will use less memory while intensively collecting on showing tooltips.

I see what you mean but for now I haven't planned this but this could be
an interesting idea to know how performs your comp near your friends
comp/mods, its a good idea but I have to think of a possible implementation
because that is much than simply adding a small & simple option. I could
also think of an LibGraph implementation so to help visualizing usages
upon the time.

Anyway thank you for your suggestion, that's always good to receive
creative feedbacks like that.