Why does HitsMode use so much memory (especially during raids)?
HitsMode is an evolution of a very old code base, first created just a few months after WoW was released. It has grown by leaps and bounds over the years, with literally over 300 separate options at this point. Unfortunately, the add-on generates a great deal of “garbage” (programmer term for temporary memory used while processing). Additionally, algorithms such as early exit aren’t used (this would lower processor usage if you’ve turned off a lot of the combat log). HitsMode would require a complete rewrite to solve these issues, and that isn’t going to happen (I simply don’t have the time). All the extra memory usage shouldn’t impact your performance if you have a decent amount of RAM, so just ignore it. This is particularly bad during raids, which generate thousands of lines of combat log per second. There are a number of other things that just aren’t going to happen without a full rewrite, including: simplifying the options system; supporting raids and parties better; integrating i
Related Questions
- This especially might become an issue given your sponsorship >by UniForum. If memory serves, isn UniForum partly or >mostly concerned with proprietary Unixes?
- Are there any enhancements to the Java classes and implementation, especially in the area of memory management?
- What is the atmosphere like on Ventrilo, especially during raids?
