Re: [SMARTY-DEV] About cached paths
| From: | messju mohr | Date: | Fri, 12 Sep 2003 14:42:25 +0000 |
| Subject: | Re: [SMARTY-DEV] About cached paths | ||
| References: | 1 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-1866@lists.php.net to get a copy of this message | ||
yes i noticed that also. i'd vote for using path caching for plugins
and maybe for auto-filenames of compiled templates but not for
auto-filenames of cached pages.
monte implemented the path-caching so i'm interested in his thoughts
on this issue.
greetings
messju
On Fri, Sep 12, 2003 at 04:00:35PM +0400, Konstantin A. Pelepelin wrote:
>
> Hi!
>
> Some days ago I've put a project "into production"
>
> Today look into _smarty_cached_paths directory, and some of the files are
> big enough to worry me. The biggest files are files named by most widely
> used templates - navigation menu (300k) and search page element with one
> item (500k). I have a doubt if that big cache files are really an advantage
> in file paths construction.
>
> Should they be so big? Site has many cache groups (to make it possible
> caching of every possible query), can it be the reason.
> Example:
>
> http://games.dailytelefrag.com/index.php?type=search&query=age&genre_id=2
> I can add that noted templates are fetch()'ed in a plugin (to be cached
> separately) but some other files in cached_paths are big too, while
> corresponding files are fetched in normal way.
>
> Konstantin A. Pelepelin