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 id
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...
- Origina
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
propor
