[phplib-trackers] [ phplib-Feature Requests-577332 ] Template caching

[SourceForge.net <no...@so...>]

Feature Requests item #577332, was opened at 2002-07-04 11:32
Message generated for change (Settings changed) made by powerstat
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=403614&aid=577332&group_id=31885

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Priority: 5
Private: No
Submitted By: Dipl.-Inform. Kai Hofmann (powerstat)
Assigned to: Nobody/Anonymous (nobody)
Summary: Template caching

Initial Comment:
It would be nice to have a kind of template output
caching to speed up template processing. For example
some template outputs will only change in 24 hours or
more.
This will not work for all templates but for a lot it
might bring significant improvement - especially in
combination with php-accelerator.
Maybe it is helpful to take a look at the "Smarty 2.x"
template engine, also please take a look at the
PHP-Accelerator Benchmarks at
http://www.phpinsider.com/benchmarks/


----------------------------------------------------------------------

Comment By: Joe Stewart (joestewart)
Date: 2002-11-01 17:26

Message:
Logged In: YES 
user_id=77269

I thought phplib stood up pretty well on the phpinsider
benchmarks.

Another interesting set of template benchmarks:

  http://www.massassi.com/bTemplate/benchmarks/



----------------------------------------------------------------------

Comment By: Richard Archer (richardarcher)
Date: 2002-08-12 09:00

Message:
Logged In: YES 
user_id=279311

Loading in a file (or even several files) from disk won't be
the bottleneck in a typical template-based page.

The bottleneck will usually be the database accesses
required to create the content. And to a limited degree the
regex manipulations to insert the content into the template.

If you're running sessions too, you also have the PHPLIB
per-page overhead for pulling the session data out of the
database.

In the scope of PHPLIB, the usual consideration of caching
is how to *prevent* it, rather than implement it :)

 ...R.



----------------------------------------------------------------------

Comment By: Dipl.-Inform. Kai Hofmann (powerstat)
Date: 2002-08-12 08:47

Message:
Logged In: YES 
user_id=286352

I think that template caching is different from content
caching!
That because content has already filled in the template vars
and blocks.
By template caching I mean the pure template so that it must
not be loaded from disk each time - which is a performance
bottleneck!

----------------------------------------------------------------------

Comment By: Layne Weathers (layne_weathers)
Date: 2002-07-05 18:55

Message:
Logged In: YES 
user_id=278685

This is not a Template issue at all. Content caching applies 
to any page whether it's inline or template-based - even static 
HTML pages benefit from caching.

There are many caching engines out there - perhaps we can 
mention those in the documentation.

If PHPLib wants to provide a basic caching mechanism in 
8.x, let's please keep it pure.

----------------------------------------------------------------------

Comment By: Richard Archer (richardarcher)
Date: 2002-07-04 22:59

Message:
Logged In: YES 
user_id=279311

There is a patch to enable this in the file attached to:
https://sourceforge.net/tracker/index.php?func=detail&aid=450744&group_id=31885&atid=403614

This won't apply cleanly to the latest template.inc, but
should be a good starting point if you require this
functionality.

I decided against including it in the standard template.inc
because of the additional complexity... maybe I should
re-think that decision.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=403614&aid=577332&group_id=31885