DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34529>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34529

           Summary: Suboptimal analyzing of project build files
           Product: Ant
           Version: 1.6.2
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P4
         Component: Core
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [EMAIL PROTECTED]


According to profiler output gathered when running NetBeans build with JDK1.4.2
using Ant 1.6.2 it should be possible to improve Ant performance.

Constructor of Location in ProjectHelper2.ElementHadler.onStartElement is
expensive. This is because conversion between URI and file is happening here.
Perhaps it is worth to optimize Locator.fromURI assuming that most of URIs do
not contain '%' and thus avoid StringCharacterIterator use in most of cases.

I also noticed what Jesse described in bug #25767 - creating of new SAX parsers
is not for free.

RuntimeConfigurable maintains two data structures holding overlapping data -
list of attributes and map <attribute;value>. One more efficient storage can
bring some benefit.

ProjectHelper.getProjectHelper is not a hot spot but still can be a bit faster
if it checks for resource first and thries to get the stream. This will not use
exception to control the program flow. Filling of stack trace cost something in
their constructor.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to