Andreas Hartmann schrieb:
[...]
Unfortunately we need some resource-exists selector cascades in
global-sitemap.xmap to stay backwards compatible, and therefore the
pipelines are not cacheable. When I find the time I'll do some load
testing to find out what happens when we have only static and
cacheable menu XML processing.
* Powerbook G4 1.5 Ghz
* Standard Jetty setup
* 1 thread
* 20 requests to /default/authoring/index.html
2.0.1: avg. 1467 ms (41/min)
2.0.2-dev with some modifications: avg. 929 ms (65/min)
I didn't explicitly check if the menu XML is cached, but the authoring
environment feels notably faster. IMO it's worth the update. Maybe we'll
find a way to leverage caching without losing backwards compatibility
(e.g. using include fallback elements).
In fact the XML hadn't been cached, because the IncludeTransformer's
MultiSourceValidity isValid() method returns "invalid" if one of the
included sources was not found. I removed the "offending" modules from
publiction.xml. Now the XML is cached, but the load test results are
virtually identical. I'll do some more investigation.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
