Hello,

I would like to improve performance on my cocoon application. I had an idea, but I'd like to confirm that it would be useful.

On my sitemap, I have many small matchers, like:

<map:match pattern="foo">
  <map:generate type="file" src="">   <map:transform type="xslt" src="">   <map:serialize type="xml" />
</map:match>
<map:match pattern="bar">
  <map:generate type="file" src="">   <map:transform type="xslt" src="">   <map:serialize type="xml" />
</map:match>
<map:match pattern="xyz">
  <map:generate type="file" src="">   <map:transform type="xslt" src="">   <map:serialize type="xml" />
</map:match>


Would I get better performance with the following "foo" pipeline?
<map:match pattern="bar">
  <map:generate type="file" src="">   <map:transform type="xslt" src="">   <map:transform type="xslt" src="">   <map:transform type="xslt" src="">   <map:serialize type="xml" />
</map:match>

Of course, such a sitemap would be less maintainable and more difficult to debug (unless I use views, which is a nice possibility), but performance IS an issue at the moment.

If the former "foo" pipeline gets better performance, could one optimize this somehow? How?
<map:match pattern="foobar">
  <map:aggregate element="foobar">
    <map:part src="" />
    <map:part src="" />
  </map:aggregate>
  <map:serialize type="xml" />
</map:match>


Thank you very much.

--
Antonio

Reply via email to