white jetty
I am using a Weakaura to track Lava Burst which contains triggers for the spell cooldown/charges and one for Lava Surge to track resets. Additionally it contains a few conditions to make it optically more appealing. There are no custom elements.
However after a raid my Weakaura Profiling looks like this and it feels like I am experiencing performance issues:
dusty dove
!linkit
SH - Lava Burst is using waay more time than is usual.
fresh stirrupBOT
WeakAuras doesn't show anything by default, it's just the framework that lets you import or create "Auras" to display things. If you're having an issue with an Aura, and/or want opinions on it, then you need to share the specific Aura. The best way to do this is to link it through https://wago.io/.
If you only imported the aura, you may right click the aura in-game and select Copy URL and paste it here. If you have modified the aura or created your own, you may instead select Export to string... and upload the string to https://wago.io/. This does not require an account.
You can now paste the import string directly into Discord (with no other text, only the string) and a bot will import it for you and link the wago.
white jetty
dusty dove
There does seem to be a couple redundant condition checks but that shouldn't cause it to run that much more.
Only other thing I see is Condition 3 has and ALL OF check with only 1 condition inside of it.
Besides that nothing seems obvious.
white jetty
Reason for that might be that I removed a 3rd trigger some days ago that seemed weird to me (that’s when the WA already caused problems) which included a player status/health check without any specifications which made no sense to me which is why I tried to remove it to see if this might change something. I will try to find an old version in one of my backup folders that still includes that 3rd trigger, maybe that helps in some way.
dusty dove
a trigger with no options is usually there to use the information in conditions.
white jetty
This is the unedited version: https://wago.io/Z5JgHIZPq
Seems like the 3rd trigger was a leftover from older versions of WeakAura and therefore it "broke".
But i guess having that old version won't bring me anywhere closer to a solution anyway.
hybrid phoenix
people usually add those triggers as a "always active" trigger, probably because they dont know that an actual "always active" trigger exist
but yeah this aura is not the problem, the problem is somewhere else possibly in your system or something else attributing all that time to that aura
can you do another profiling, as short as possible where you experience issues