I had an issue a week or so ago that I just remembered.
After a Malygos fight I tried to remove some entries in the DPS view by CTRL + ALT + left click on all non-drake entries (merge with pets obviously off) and quite a few lines that I did not click on were also removed. After removing all players, pets, totems etc, I was left with only about 8-10 entries for drakes, but had 15-20 lines with drakes before I started removing entries. The difference was a bit too big for me to have screwed it up and clicked on the wrong lines... I definitely got the feeling that Recount sometimes removed multiple entries when I clicked and not lines directly next to each other.
- Registered User
Member for 12 years, 7 months, and 6 days
Last active Fri, Oct, 4 2013 21:32:22
- 0 Followers
- 10 Total Posts
- 0 Thanks
Jun 22, 2008As I understood it those are real time events, i.e. they report when a boss dies and the loot is distributed.Posted in: Raid AddOns
I was thinking of a summary report that could be run after a raid, similar to the exports.
Jun 21, 2008I'd like to request a simple guild/officers (or any other channel) chat loot report.Posted in: Raid AddOns
My idea was of something that would report the loot from a raid into (primarily) the guild chat. A suggestion to a format would be a single header line followed by a line per loot as:
<instance> <start time> - <end time>
<player name>: <loot link> from <boss>
Perhaps sorted on looting time or per player.
Jun 16, 2008Splitting Ace3 into components shows that it is AceTimer-3.0 that takes up a lot of CPU there.Posted in: General AddOns
AddonManager shows about the same amount of CPU on AceTimer as on Recount, but the number don't match Expo. AM shows about 17000 ms on AceTimer and 17000 on Recount, but since that roughly adds up to what Expo says on Recount I guess that is just down to how they allocate the time to a lib.
Expo on Recount shows for about a minute measuring interval when wow hangs completely (Real time and killing a single mob):
:FreeTable - 34.294 sec - called 3968 times - time/call 8.6 ms
:GetTable - 0.746 sec - 1246 times - 0.599 ms per call
:ResetFightData - 0.033 s - 49 times - 0.673 ms per call
Wow hangs about half a second after the mob dies.
When resetting data in Recount the problem goes away immediately. Then the top method in Recount is :TimeTick at 0.006 ms.
Again this happened when I had been on a raid the day before and not resetting the data.
Jun 15, 2008I'm having a random situation were Recount/Ace3 takes up an awful lot of CPU and in practise freezes my wow for anything between 2 seconds to a minute or so. Average is about 5 seconds.Posted in: General AddOns
I first got the result for Recount and Omen, but after removing the Ace3 embedded libs and using Ace3 standalone, it showed up as Ace3 and Recount.
The other 50 or so addons: 0.9%
I can't reliably reproduce this, but when it happens it is relatively common that I have been on a raid the day before and not reset the Recount data. I then use my pet and go and fill up soul shards. After a mob dies, I sometimes get a freeze for 2-5 seconds and Ace3 and Recount have during the freeze used up hundreds if not thousands times more CPU than usual in a raid.
I have split Ace3 into its components to see if I narrow it down which Ace3 component it is that is getting hammered. I have not been able to reproduce this since the split though. I guess it is a bug in Recount that calls something in Ace3 an awful lot of times though.
Jun 14, 2008Posted in: Raid AddOnsQuote from Phanx »
Disembed your libs and then do your test again; performance metrics gathered with embedded libs have almost zero meaning.
Ok, removed the embedded Ace3 libs from Omen and Recount. This time it froze for about 30-40 seconds and even when I ALT-Tabbed out to Windows one of my CPU cores were at 100%. The result this time was:
The other 50 or so addons: 0.9%
I guess this is the wrong thread then. Is there a Ace3 libs thread?
Jun 12, 2008I have a situation with massive CPU usage in Omen2 and Recount and where I can't see any consistent pattern in what triggers it.Posted in: Raid AddOns
Sometimes Wow 'freezes' for 2-10 seconds. I have managed to track it down to CPU usage of Omen2 and Recount by using the addon AddonManager where you can see (and reset) the CPU usage per addon. I reset all figures to zero and triggered the race condition and the result was that Omen2 and Recount took up about 93% of the CPU used by addons during that period. Normally the CPU figures for those two addons would be about 1-2% each.
It seems to only happen when I'm in a group or with a pet (warlock), but I'm not 100% sure of that.
The other day when I managed to measure it, I could trigger it over and over again killing mobs using a pet. It always happened immediately (maybe half a second) after killing the mod. I kept happening until I did a /recount show and reset the data. Omen2 and Recount had identical CPU usage in the range of several hundred times more than normal for them.
It had also happened a number of times when I opened all bags, but have never managed to measure that, so could of course be some other addon that is getting out of hand then.
This is of course extremely annoying when it is happening in the middle of a fight in a raid...
I have guessed there is something dodgy in one of Ace3 libs that they both use. Both addons embed these:
If there is anything I can do to get more useful information please let me know.
Apr 2, 2008It seems like the wiping of threat during a fight, like on Hydros or Leotheras isn't working. Maybe I'm way off here (I have never written any addons) and I have not tested this in any way, but...Posted in: Raid AddOns
in the function ThreatLib.OnCommReceive:RAID_MOB_THREAT_WIPE this line exists:
"if (cooldownTimes[mob_guid] or 0) > 15 then"
I think however it should look something like:
"if GetTime() - (cooldownTimes[mobName] or 0) > 15 then"
otherwise cooldownTimes[mobName] will not get a value and hence the function will never reset the raid aggro on the mob.
or I'm completely wrong.
- To post a comment, please login or register a new account.