forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: [jira] Commented: (FOR-803) Profile new dispatcher plugins
Date Fri, 10 Feb 2006 00:49:56 GMT
Thorsten Scherler wrote:
> David Crossley escribi??:
> > I started doing some "Cocoon Profiler" on site-author.
> > Processing index.html four times then looking at cprofile.html
> > 
> > Compared Dispatcher-enabled site-author with the profile
> > of skins-based site-author running on another port.
> > 
> > Still not sure how to interpret results, but
> > here are some initial observations.
> > 
> > Using the default theme ...
> > 
> > Some pipelines seem to be requested twice or more
> > for each page view, e.g.
> > resolve.contract.html.siteinfo-feedback
> Yes, that is how the dispatcher is working so far. As soon as you use
> twice a contract it will be included twice and requested twice. 
> > Using the pelt theme ...
> > 
> > Seems to process an extra resource called license.html
> > and its associated pieces.
> ??? wow, that is a new finding. Thx. No clue ATM why. Which uri did you
> request originally?

See above. I always use index.html and no other requests.

It is also useful to request index.html just one time,
then look at the profiler. Some pipelines are called 25 times.
Need to increase the setting in forrest.core.xconf

To gather further statistics, do index.html four times.

> > Total of about 100 pipelines were processed compared
> > with about 45 pipelines for the skins-based site
> > and about 40 pipelines for the default dispatcher site.

My main query was why are there 100 pipelines using
the pelt theme and only 40 using the default theme?

> The idea is that contracts are standalone and self containing that has
> the downside that some information are requested more then once.

Not so bad if all of the pipelines are cached.

> I am
> unsure how we can reuse the pipes more efficient since I reckon they
> cause the build time to rise. Maybe we should think about a dispatcher
> generator that will request the dataUri and aggregates the data
> requested by the structurer. From there we can request this data from
> the dispatcher transformer. That would help controlling that contracts
> (if using the same dataUri) would use only *one* pool (aggregated by the
> dispatcher generator) and the data get requested *only once*.

Can we still change the data and Forrest would reflect
that change? Rapid application development.

> Thanks David, you are now the official dispatcher "profiler" for me (no
> strings attached). ;-)

I see the smiley, but please, no. We all need to try
to interpet it.


View raw message