Re: VisibleMemberMap.java possible performance improvements

2013-11-25 Thread Michael Simacek
Ok, so are these three items I mentioned bugs in the original implementation? And I should report each of them separately and try to fix them in the original implementation, right? Or should I propose my patch (or part of it) as a fix for them (with tests ofc)? Michael Simacek

Re: VisibleMemberMap.java possible performance improvements

2013-09-25 Thread Michael Simacek
Thank you for your help, Jon. I've rewritten it a bit (also had to change the Util.executableMembersEqual method to fix some issues), so now all the tests should pass and I have fixed some other bugs. Now the order of classes is the same and order of interfaces is mostly the same. I tried to get

VisibleMemberMap.java possible performance improvements

2013-09-19 Thread Michael Simacek
Hi, I thought about improving performance of the default doclet implementation a bit. According to profiler results, most of the CPU time is spent in constructing the member map in VisibleMemberMap.java. So I've rewritten part of the VisbleMemberMap and reduced the javadoc run time to 60-70% of