Re: [SMARTY-DEV] About cached paths

i removed the path-caching. i couldn't measure any significant performance gains with it that would justify the complexity that comes with the additional _smarty_cached_paths-files. of course i can not test all conditions and all types of setups so anybody who may encounter noticable performance losses by my change please report it here. greetings messju On Fri, Sep 12, 2003 at 10:53:32AM -0500, Monte Ohrt wrote: > This vote sounds fine to me... maybe we should stick to caching paths to > often-used files, which would exclude cache and compile file paths. > > Monte > > On Fri, 2003-09-12 at 09:42, messju mohr wrote: > > 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