Scott Hernandez wrote:
Good work. That is one that needed to be optimized :)
Do you have profiler stats/results on other most called, or time most spent
in, functions? It would be good to list them so anyone out there could step
up to challenge themselves with optimizing those functions. Just an idea...
Unfortunately, I haven't hooked up the "copy to clipboard" functionality in nprof, so all I can provide is a screenshot. ;)
I can probably summarize the trouble spots by hand- the NAnt-bootstrap build would be a good candidate. My goal right now is to catch the low-hanging fruit for a general <solution> build to match (or exceed) VS.NET's compilation speed wherever possible.
Matt.
----- Original Message ----- From: "Matthew Mastracci" <[EMAIL PROTECTED]>
I just checked in a change to fileset scanning that eliminates a large chunk of time (checked via profiling) during many of the common NAnt operations.
One of the biggest losers on the profiling run was Regex.Match(), called many, many times during a build. The new code replaces a good proportion of these with CompareInfo.Compare() calls, reducing the overhead dramatically.
Instead of converting all <fileset> includes to regexes, the new code
will only convert those that actually contain wildcards.
begin:vcard fn:Matthew Mastracci n:Mastracci;Matthew org:aclaro Softworks, inc. adr:;;1900 a - 11 St. SE;Calgary;Alberta;T2H 3G2;Canada email;internet:[EMAIL PROTECTED] title:Software Developer tel;work:(403) 299-6612 x-mozilla-html:FALSE url:http://www.aclaro.com version:2.1 end:vcard
