Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (asf.osuosl.org: 207.114.11.197 is neither permitted nor
 denied by domain of perrin@elem.com)
Subject: Re: Clearsilver Templates
From: Perrin Harkins <perrin@elem.com>
To: Praveen Ray <praveenray@yahoo.com>
Cc: modperl@perl.apache.org
In-Reply-To: <20050818153902.7438.qmail@web30512.mail.mud.yahoo.com>
References: <20050818153902.7438.qmail@web30512.mail.mud.yahoo.com>
Content-Type: text/plain
Date: Thu, 18 Aug 2005 11:48:49 -0400
Message-Id: <1124380129.5161.676.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Thu, 2005-08-18 at 08:39 -0700, Praveen Ray wrote:
> I suspect its because we've written a large number of
> moderately complex macros

Could be.  You can probably test this fairly simply by globally removing
the macro calls and benchmarking.

> Or, is it the fact that TT uses string concatenation for
> every MACRO and BLOCK's output?

Not likely, although that may increase the memory used.

> I wish TT could write onto output stream as the output is
> generated instead of first building a giant string.

There have been patches on the list to flush output periodically, but I
don't think they remove all buffering.  The buffering is what makes
things like filters, wrappers, and exception handling possible.

However, TT is pretty hackable if you want to change that.

- Perrin