On Wed, 7 Jun 2000, Stas Bekman wrote:
> On Wed, 7 Jun 2000, ___cliff rayman___ wrote:
>
> >
> >
> > Stas Bekman wrote:
> >
> > >
> > >
> > > Per your request:
> > >
> > > The handler:
> > >
> > > query | avtime completed failed rps
> > > -----------------------------------------------
> > > single_print | 110 5000 0 881
> > > here_print | 111 5000 0 881
> > > list_print | 111 5000 0 880
> > > concat_print | 111 5000 0 873
> > > multi_print | 119 5000 0 820
> > > -----------------------------------------------
> >
> > not very much difference once stuck in a handler.
> > obviously multi_print is both ugly and slow, but the rest should be used by the
> > discretion of the programmer based on the one that is easiest to maintain in
> > the code.
>
> absolutely. I'd also love to know why is it different under the handler.
> (talking about relative performance!)
Because as I said - the method dispatch and the overhead of the mod_perl
handler takes over. multi-print is the only one that has to call methods
several times. The rest are almost equal.
This also demonstrates some of the value in template systems that send all
their output at once, however often these template systems use method
calls too, so it all gets messed up.
--
<Matt/>
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org http://xml.sergeant.org
