Jörn Nettingsmeier schrieb:
Andreas Hartmann wrote:
Andreas Hartmann schrieb:
I did some more tests - maybe I did missed something before, but now I
get different results which resemble my expectations.
* same setup as above
* Lenya 2.0.2-dev without modifications
* Fallback source URI caching enabled
a) standard publication.xml: avg. 1200 ms
b) publication.xml contains only modules with menus: avg. 800 ms
In case b), the aggregated menu XML is cached because the include
transformer didn't come across any non-existing sources and therefore
the validity could be computed.
At the moment b) can't be enforced because the publication.xml entries
are also used for i18n. But I'm confident that we would find another way
to assemble the modules i18n catalogue.
WDYT - can we require that publication.xml contains only modules which
provide a menu, and throw an exception otherwise?
nah.
If the patch for https://issues.apache.org/jira/browse/COCOON-2166
proves useful (or we find another solution), this will fortunately not
be necessary.
-- 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]
