You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #4

  merah Jan 03, 2011 at 19:34 UTC - 0 likes

  anyway thank you for the suggestion, I will let this ticket open because I had in mind too to add stats, maybe graphs as seen in auctioneer, yet I have two new babies SpamBayes to work on, they are going to be great, gif zem a try ;)

  Last edited Jan 03, 2011 by merah
• 

  • Reply
  • #3

  merah Dec 31, 2010 at 13:40 UTC - 0 likes

  the colorgradient like other values updates to each threshold ticks so it last until the mod uses less resources

  There is no way yet to see how much previous peaks the mod used to do, maybe if I find a simple way to add it I will add it, I need something like a library building graphics for example so I can add this feature without to much enlarging the mod size because this feature requires for sure more memory

• 

  • Reply
  • #2

  Everdreamer Dec 29, 2010 at 15:36 UTC - 0 likes

  Thanks for the detailed explanation :D

  I understand the memory part and garbage collection, but was confused at the CPU usage part. Now I see there is no Down arrow on CPU, can you explain a bit how the colorgradient on CPU works? Is it also delta(usage)/delta(time) ?

  In my previous example, when addon B suddenly behaves bad, I know Broker_CPU will show it orange or red, but how long will the "bad color" last? Will the color return to green next second because addon B resumes its normal behavior? If so, is there a good way to monitor this kind of peak behavior?

  Last edited Dec 29, 2010 by Everdreamer
• 

  • Reply
  • #1

  merah Dec 28, 2010 at 12:28 UTC - 0 likes

  About the documentation I believe I have said it all already, to disembed a library you have to delete it from the addon embedding it and install the library like a normal addon in the \AddOns folder

  % is the difference between the old (at last threshold tick) and current value / 10 as seen in performancefu, its on the first page since a few days ago, so If addon A keeps using 10ms CPU time every second for 10 mins, is the 1% shown constantly in the tooltip? yes, because bkcpu retrieve datas each seconds (by default with a tip update threshold to 1) so you have the current usage

  Considering addon B which uses 1ms per second in general but sometimes uses 100ms in a second, it is unstable and may cause a freezing problem. Then you will see it because the CPU count does not reset until you disconnect or reloadui and anyway if a mod use that much 100ms in one second he will most likely appear orange or red because the colorgradient is based on the value evolution, not the current amount

  The up arrows value are just here to represent how big is the new value near the old, if > then red arrow, if less a green arrow and if the value did not change, a yellow bar, its just another way of providing color gradients.

  There is never a green arrow on CPU (on just in some rare case when the client is probably re-evaluating the usages) because an addon cannot technically use the cpu less than it has already done, if you travel from X to Y and it tooks 5min, it wasn't 1 min right ?
  Memory has green arrow because the amount of memory is sometimes bigger than the current real one.

  To say it simple, memory has a lifetime, and Blizzard set a limit in the client so your mod cannot technically use all of your 12GB RAM.
  So now they have set a 100Mb limit allowed for mods, how to be sure X mod will not ninja all of the free memory ?
  This is the garbage collection that happens regularly and you see represented in Broker_CPU when all mods gets a green arrow on the memory, the client is collection all the "dead" memory (called garbage)
  When a mod produces to much memory its called the garbage memory which your client collect silently

  The goal is then for a mod to produce the minimum of this dead memory so the client collection will be quicker, a mod with a tiny memory can show better than a bigger one at a first look but if you see it generate 10Mb memory and then the client collect also these 10Mb, means the mod is producing 10Mb of dead memory thats worse then the bigger mod producing its 200KB of dead memory, they were collected quicker

  if do you want a sample you can try broker_cpu release12 versus alpha15 with icons, the release will create more garbage because I have made an error by creating two tables in a heavy loops and I did not reuse them so they are waiting to be collected

  If you still don't understand I recommand you to read
  http://lua-users.org/wiki/OptimisationTips
  http://www.lua.org/gems/sample.pdf

  They explain this better then me for sure