Another issue of having too many pipelines. As i understand in the sitemap is generated into a java class. And the various matchers within a pipeline(s) are really a bunch of if-else if statements. So the more matchers you have (to match to a pipeline or various paths within a pipeline) your going to have a large series of if/else statements. And... since this uses string compares and wildcards and... if there's alot of these if else if statements it will lead to performance issues.
It may help to break things up with sub site maps to help limit the searching. Or put the most likely pipelines to get hit first and the least likely last... In a message dated Sun, 13 Oct 2002 18:03:02 +0200, [EMAIL PROTECTED] writes: > > > Hi Ivelin, > > > -----Original Message----- > > From: Ivelin Ivanov [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, October 13, 2002 4:25 PM > > To: [EMAIL PROTECTED] > > Subject: [Q] Pipeline best practices > > > > > For example how many pipelines in a sitemap are reasonable? > > How do one chooses when to put multiple matchers in one pipeline vs > > splitting them in separate pipelines. > > Some of the reasons are: > > - different error handling > - different types of pipelines (caching, profiling) > - internal-only use > - the use of different expires attribute > > Does anybody know some other reasons? As far as I know there is no > difference in performance. > > Regards, > Reinhard > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. < TITLE="http://xml.apache.org/cocoon/faq/index.html>" >TARGET="_blank">http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: > <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
