-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
current memory usage #350
Comments
Did you test on a Dummy, or in a raid? (The dummy is pretty hard on a populated server....lot's of events from hundreds of players...didn't have time to test in a raid unfortunately... While those aren't good values...they aren't bad either...Some events overlap - so you cant bei 100% sure which event really increase the memory...(and this also leads to the conclusion that you can't just add all single values) Maybe I should add a total memory increase within this 45 seconds interval....might be a good idea. |
profiling crashed WoW after enabling in LFR :D will post a comment after testing in LFR EDIT: and again , no way for profiling in 25 man raid :) :D |
Damned....maybe 5 second intervals was a little to enthusiastic...maybe 15 seconds are a better choice |
any idea why the usage value is sometimes negative? |
Garbage Collection |
so during the calculation a garbage collection started ?^^ |
Well...it's the only rational explanation I got :D I noticed this too...tried to figure it out, but didn't manage to....GC in Lua is strange....never found a good source on how it really works...it has a pretty bad GC (else tables wouldn't be so much of a problem)...Java is way better, but still...I really can't explain it... |
currently I tested two similar functions in memoery usage & execution time and got interesting results. functions:
for 900000 iterations: keyPressed1 uses the half of the memory of keyPressed2 the big change is only the iteration method and while keyPressed1 does not create new tables, keyPressed2 does but it faster with this method. While measuring memory I did a garbagecollect between the measurements. |
for 35 seconds:
(removed SPELL_DAMAGE for testing, so it doesn't shows up below)
Any ideas to lower the values? tested with the lowest updateInterval Value
The text was updated successfully, but these errors were encountered: