To TilesTool or not to TilesTool. That is the...

[je...@optonline.net]

I spent part of the afternoon considering using the TIlesTool.  Right now I am using straight Velocity templating, but like the versatility of the Tiles Tool.  I checked the dev list and the biggest concern that I see is comment on speed below.  I was wondering if people had further information on performance/comparisons.  I would not want to use it if it ran half as fast as straight velocity templating.

>hmm.  though it's sure to be a relatively negligible one, this is gonna be a
>performance hit (from recreating/reinitializing the tools for each tile).
>still, you're right, each tile probably should get it's own context to avoid
>unforeseen interactions.  if someone is really concerned about being as fast
>as possible while doing layout rendering, we have options besides Tiles.


I am working off of nightly builds (including struts post 1.1).   I have not tried the TilesTool yet, but was hoping to get peoples' views and if there are any open issues.  Is there a decent example out there of it working.  I know a few partial examples are on the dev list.

I am hoping ot start fooling around with it over the next couple days.

Thank you for your insite.

John



---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org

Re: To TilesTool or not to TilesTool. That is the...

[Nathan Bubna <na...@esha.com>]

jeichels@optonline.net said:
> I spent part of the afternoon considering using the TIlesTool.
> Right now I am using straight Velocity templating, but like the
> versatility of the Tiles Tool.  I checked the dev list and the biggest
> concern that I see is comment on speed below.  I was wondering
> if people had further information on performance/comparisons.
> I would not want to use it if it ran half as fast as straight velocity
templating.

i have no performance/comparisons and don't currently use the TilesTool
myself, but i can say that unless you have a *lot* of tools and/or some very
heavy lifting happening in their init() methods, then my comment you quote
below would not cause a 50% hit in performance.  :)

> >hmm.  though it's sure to be a relatively negligible one, this is gonna be
a
> >performance hit (from recreating/reinitializing the tools for each tile).
> >still, you're right, each tile probably should get it's own context to
avoid
> >unforeseen interactions.  if someone is really concerned about being as
fast
> >as possible while doing layout rendering, we have options besides Tiles.
...

and to elaborate on "options besides Tiles", there is the
VelocityLayoutServlet and the ever-useful #parse( "foo.vm" ).  these use the
same context and toolbox and do not involve URL connections, so they should
generally be faster.

also, with regards to recreating/reinitializing the tools for each Tile...  i
plan to get tool pooling done for VelocityTools 1.2.  that may be a ways off,
but when it comes, then that should help a bit too.

Nathan Bubna
nathan@esha.com


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org