> The cases you've described above all happen only once (at startup
> time). Assuming that we could safely optimize these cases, would it
> really make a significant difference?
It wouldn't.
While you were away, I did some profiling of the startup (since people
complained), and it turns out that the time is mostly spent in :
- Crimson, because it's used in validating mode
- introspecting and doing various things in the XML mapper (no surprise)
> To influence the performance of Cocoon, we'd want to look at the Resources
> implementation. It's been worked on, but I would certainly not say we've
> really optimized it yet. And reducing the number of calls to
> getCanonicalPath() sounds like a good strategy -- as long as it can be
> done safely.
getCanonicalPath is called only under Windows (for case sensitivity
checking).
More profiling showed that the resources were fast enough.
Remy
