Are you tired of your current antispam solution that requires regular spam database updates without guarantee of success ?
Want to experiment the power of bayesian filtering emails with chat messages in your game ?
Looking for an antispam working with ALL languages ?
You find your antispam too opaque and you are looking for more transparency ? SpamBayes is born for you
A lightweight Data Broker plugin to visualize AddOn CPU/Memory usage, Framerate and Latency
New Now uses a dropdown menu by Blizzard instead of dewdrop
New For 2011, I'm revisiting the addon to correct known problems, improve the code and make use of resources to a bare minimum
Usages:
Type /cpu, /brokercpu or /broker_cpu to show usage (or click the button with Broker bars)
Helps/Tips:
s/ms
a value representing the access time to processor since you entered the world or a reloadui
KB/MB/Ko/Mo
a value representing the current amount of memory used
But don't focalize on addons using a high number of memory, the screenshot of Carbonite vs QuestHelper shows you why, while Carbonite allocates more memory it has a tiny memory garbage creation and less cpu usage than QuestHelper that allocates less memory but has an horrible garbage creation, Carbonite shows a better control on performance than QuestHelper which increases the client's job to collect garbage memory and if you're experiencing freezing problems ingame you may look at an alternative to such bad boys, this is why it is useless to color gradient the amount of memory because you will just get an unreadable rainbow, the mod rather gradient the next % value explained below which is the most important)
%
a value representing the difference between the old and current usage / 10
Like a speed meter you can use to compare X versus Y plugin, to check how performs your code, etc... if your mod goes red here, it most likely sucks hard!
BrokerCPU works with most LDB display, for a complete list see here
CPU profiling which is by default to OFF in the Blizzard client should remain OFF when you don't need it
Prefer the use of standalone libraries so BrokerCPU can report usage from addons and libraries separately, to do so follow these tips:
You just install a standalone library like any other addon in the same Interface\AddOns\ folder
The library must have a .toc file and the library folder must have the same name than the .toc file, example with DewdropLib the path should looks like Interface\AddOns\DewdropLib\DewdropLib.toc
Then the longuest part is to remove the library you just installed in standalone from every addon you use that could embed it, then you are sure that only the standalone library is called and the consumed resources are correctly belonging to it.
Some libraries are NOT to dis-embed, so if do you see the most popular embeds LibDataBroker, AceLibrary, LibStub, CallBackHandler, just leave them embedded, they are not designed to be standalone (If a library does not provide a .toc file it's not designed to be standalone)
Bugs/Suggestions:
Must be reported in a Curseforge ticket, comments won't be considered for these types of requests
And remember to post as much informations possible
Revision: 28
Author: merah
Date: 13:17:23, jeudi 16 juin 2011
Message:
update: latency home to latency world (ticket #4)
fix: nil error (ticket #5)
----
Modified : /trunk/Broker_CPU.lua
Revision: 27
Author: merah
Date: 21:10:48, jeudi 9 juin 2011
Message:
version notification while resting
----
Modified : /trunk/Broker_CPU.lua
Revision: 25
Author: merah
Date: 08:41:13, mercredi 27 avril 2011
Message:
v. v.
----
Modified : /trunk/Broker_CPU.lua
Revision: 24
Author: merah
Date: 08:38:20, mercredi 27 avril 2011
Message:
toc toc
----
Modified : /trunk/Broker_CPU.toc
Revision: 22
Author: merah
Date: 12:22:17, dimanche 20 mars 2011
Message:
workaround the blizzard tips no more showing up
----
Modified : /trunk/Broker_CPU.lua
Revision: 21
Author: merah
Date: 10:42:27, dimanche 20 mars 2011
Message:
enlarge memory gradient limit
----
Modified : /trunk/Broker_CPU.lua
Revision: 19
Author: merah
Date: 22:04:22, mardi 4 janvier 2011
Message:
my toon
----
Modified : /trunk/Broker_CPU.lua
Revision: 18
Author: merah
Date: 17:27:27, samedi 1 janvier 2011
Message:
fix nil error sometimes on reloadui
fix gametip download colorgradient set too low
----
Modified : /trunk/Broker_CPU.lua
Revision: 16
Author: merah
Date: 15:51:30, mardi 28 décembre 2010
Message:
old function rename
reminder to not leave profiling turned on
----
Modified : /trunk/Broker_CPU.lua
Revision: 15
Author: merah
Date: 02:02:25, mardi 28 décembre 2010
Message:
- arrange colors for both tips
- collect garbage on left click and show amount collected
- incoming and outgoing bandwith collection
- more decimals
----
Modified : /trunk/Broker_CPU.lua
Modified : /trunk/Broker_CPU.toc
Deleted : /trunk/CallbackHandler-1.0.lua
Added : /trunk/LibCallbackHandler-1.0.lua
Modified : /trunk/LibDataBroker-1.1.lua
Deleted : /trunk/arrowa.tga
Deleted : /trunk/arrowb.tga
Deleted : /trunk/arrowc.tga
Deleted : /trunk/icon.tga
Added : /trunk/tt_arrowa.tga
Added : /trunk/tt_arrowb.tga
Added : /trunk/tt_arrowc.tga
Added : /trunk/tt_icon.tga
Revision: 14
Author: merah
Date: 15:15:11, samedi 25 décembre 2010
Message:
- hooks to forbid critical APIs down to only one; ResetCPUUsage(), which seems the only one causing problems
- the hook warning is now moved after the call of the function so you don't get a warning if the mod hasn't called it
- introducing customizable decimals, you can now choose from 0 to 3 decimals for all 4 columns (has an impact on resources usage)
- LibQTip cpu usages significantly reduced, now before using SetCell the mod checks if the string has changed
- the maximum columns used by LibQTip is down from 11 to 8
- paddings are not more string based, they are done with a minWidth through LibQTip
- fixed a memory sorting mistake with GameTooltip and cpu profiling enabled
- fixed important memory garbage creation with arrow icons, they are now performing better
- GameTooltip values are now colored ala LibQTip
- addon names an rank are now colored for both Tips
- fixed mistakes in the code profiler in-code-comments
- issue a warning if cpu profiling is enabled on enter world or reloadui because people could wrongly think this is a feature provided by BrokerCPU instead of Blizzard
----
Modified : /trunk/Broker_CPU.lua
Modified : /trunk/Broker_CPU.toc
Revision: 12
Author: merah
Date: 02:42:01, lundi 20 décembre 2010
Message:
return value for hooks
----
Modified : /trunk/Broker_CPU.lua
Revision: 11
Author: merah
Date: 20:53:06, dimanche 19 décembre 2010
Message:
-nulled some garbage produced by concatened strings like addon names, positions, gives better perf sending them to a recycle table
-changed string_format to :format which is faster
----
Modified : /trunk/Broker_CPU.lua
Revision: 10
Author: merah
Date: 21:39:58, samedi 18 décembre 2010
Message:
- dewdrop removed for uidropdown
- rebuilt the command line system
- many corrrections to performance mistakes
- fix deprecated QTip:ReleaseColumn
- scans only active addons, an event catches LoD one
----
Modified : /trunk/Broker_CPU.lua
Modified : /trunk/arrowa.tga
Modified : /trunk/arrowb.tga
Modified : /trunk/arrowc.tga
Modified : /trunk/icon.tga
Revision: 8
Author: merah
Date: 01:20:44, lundi 13 décembre 2010
Message:
ensure apis are dedicated to the mod
----
Modified : /trunk/Broker_CPU.lua
Revision: 6
Author: merah
Date: 20:14:53, dimanche 12 décembre 2010
Message:
warning for punks forcing the collect of cpu and mem usages
----
Modified : /trunk/Broker_CPU.lua
Revision: 5
Author: merah
Date: 17:49:02, dimanche 12 décembre 2010
Message:
small changes
----
Modified : /trunk/Broker_CPU.lua
A lot of addon authors report that the API this addon is based on is unreliable (when I report to them their addon was reported too high), however it must be at least partially reliable since I saw tangible results: e.g. Recount gave noticeable FPS increases when it was replaced by tinyDPS based on info from this Addon, or I identified that dynamically created groups in aura addons have extremely high CPU usage compared to static groups and one can not see it only as a number on BrokerCPU but also on tangible FPS increases.
Originally posted by Annekynn I second this. World latency is the more important value, so if given a choice between the two think most would rather see World.
Id like to see both seperated by a slash / maybe. i.e. 100ms/300ms