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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25778

[PATCH] Minor optimization for ComponentHelper.initDefaultDefinitions

           Summary: [PATCH] Minor optimization for
                    ComponentHelper.initDefaultDefinitions
           Product: Ant
           Version: 1.6.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


CPU profiling of repeated runs of small Ant scripts in the NetBeans IDE (which
keeps classes loaded in the same VM between runs) showed a noticeable amount of
time being spent in ComponentHelper.initDefaultDefinitions, loading
defaults.properties (for both tasks and types) from ant.jar and parsing it. This
patch caches the result statically in ComponentHelper.

I *think* CH.iDD() is only called once per build, from Project.init() on the
entry project (not subprojects), so regular command-line usage would not
benefit. However any tool that keeps Ant classes loaded in the JVM between
builds would benefit. Should be harmless for command-line Ant except for slight
additional memory usage to hold the extra two Properties objects.

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

Reply via email to