Community
Participate
Working Groups
In profiling a load-time weaving configuration from HEAD, I found that 9% of total time (over 10% of weaving time) is spent in org.aspectj.weaver.Lint.clearSuppressions(), mostly from use inside BcelClassWeaver.match I made a small change in the parts of BcelAdvice that clear suppressions to save the list that was cleared and to only clear these. This alone saves about 15% of total CPU time in start up on my sample configuration.
Created attachment 31681 [details] Patch to weaver module that significantly reduces performance impact of supressing lint warnings (about 20%)
made it into RC1 by the skin of its teeth! I'm currently testing an almost identical solution to your patch (which I added before the patch was attached to the bug report). If the bar stays green I'll put it in.
fix now in tree
fix available