On 8 Jun 2000, Stephen Zander wrote: > As Matt has already commented, in the handler the method call > overheads swamps all the other activities. so concat_print & > aggrlist_print (yes, method invocation in perl really is that bad). > When you remove that overhead the extra OPs in aggrlist_print become > the dominating factor. Perhaps it would be worth testing the horribly ugly: Apache::print($r, <output>); Rather than plain print(). -- <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
- Re: Template techniques [ new... Perrin Harkins
- Re: Template techniques [ new... Greg Cope
- Re: Template techniques [ new... Perrin Harkins
- Re: Template techniques [ new... Randal L. Schwartz
- Re: Template techniques [ new... Ged Haywood
- Re: [performance/benchmark] printing techniques Frank Wiles
- Re: [performance/benchmark] printing technique... Stas Bekman
- Re: [performance/benchmark] printing techn... Stephen Zander
- Re: [performance/benchmark] printing t... Stas Bekman
- Re: [performance/benchmark] print... Stephen Zander
- Method overhead benchmarks [W... Matt Sergeant
- Method overhead benchmarks [W... Barrie Slaymaker
- Re: Method overhead benchmark... Matt Sergeant
- Re: Method overhead benchmark... Barrie Slaymaker
- Re: [performance/benchmark] print... Doug MacEachern
- Re: [performance/benchmark] printing techniques Perrin Harkins
- Re: [performance/benchmark] printing techniques Gisle Aas
- RE: [performance/benchmark] printing techniques Jerrad Pierce