|Subject:||[FeatureRequest] Optimise Unix::canonpath|
indeed, simply doing a directory traversal via File::Next, results in this one method accounting for 30% of the processor time.
In my test sample, 100,000 files , for which each and every file name needs canonicalizing.
And this effectively results in 600,000 regular expression substitutions being performed.
I would like to see this performance hump Ironed out, even if it means to get the performance I have to load some external XS module.
Attached: Image showing NYTProf -> kcachegrind showing the hotspot and relevant hot lines.