Hi,
"Mark F. Murphy" wrote:
>
> At 5:34 PM +0100 3/17/99, Matt Kerr wrote:
> ><random thoughts - no empirical data...>
> >
> >I would say long response times correlate more closely with large
> >repetitions than with deep component nesting. (eg. 100 reps vs. 1 pass at
> >~half dozen components...)
> >
> >If you have a lot of repetitions, or large repetitions, you may want to
> >flatten out your component hierarchy.
>
> Well, I'm not going deep at all on the components.
>
> Just a Parent Component for the entire site... which will be comprised of
> the branding component, user component, and advertising component.
We are doing this as well, this should be ok.
The performance depends much on how much variables need to be
synchronized and how often the component is accessed.
Eg if you have a ColorText subcomponent that takes 8 parameters it can
be quite an overhead if you use that in a repetition. The
synchronization is the major overhead, it occures 6 times in average
(before and after of each request/response phase). If you have a rep
with 100 iterations this can make up to 600 synchronization operations.
The synchronization overhead can be heavily reduced by the WO4
non-synchronizing components, look into the WO4 ChangeLog file for a
description. This is much like writing a dynamic element.
Helge
--
MDlink online service center
http://www.mdlink.de/
