Avoid clear caching after forum reply

Previous topic

General

Next topic

Author	Message
Michael Zeidler	Monday 13 September 2004 3:17:27 am Hi, as you might have noticed according to my previous messages, I am about to optimize the response time of my ezsite using version 3.4.1 ;). How could I avoid the clear caching when a forums entry was sent to a forum. Otherwise a new entry would initiate a publish action followed by clearing the whole template cache (equivalent to (ezsite)/bin/shell/clear-cache --clear-tpl). Of course this would make sense when you have for instance on your entry page notices about new entries in your forum. Unfortunately you cant define dependencies about what cache-files should be deleted after a certain publish action. ------------------------------------------------------------------------------------------- join #ezpublish on irc.freenode.org
Michael Zeidler	Tuesday 14 September 2004 12:52:44 am Maybe it is possible to determine what cache files are involved with a section. So when for instance the forum has its own section the publishing process for an forum entry could clear the cache only for this section. To keep on dreaming it would be nice to add this section any URLs and the additional pieces of information to reproduce the cache-block key which could be used for explicit clearing from cache. This way the page in another section which shows news about forum entries could be cleared from cache too. Btw. How is this solved on the ez.no site? I cant imagine that every forum entry clears the cache each time for the whole site? ------------------------------------------------------------------------------------------- join #ezpublish on irc.freenode.org
Ole Morten Halvorsen	Tuesday 14 September 2004 2:06:55 am Cupic, On publish eZ publish deletes all the ViewCache, however this bad behaviour is fixed in SVN (3.4 stable and trunk) and a new smart viewcache mechanism is added. After this fix only published nodes of the object, parent nodes and nodes of reverse related objects is cleared. Read about it here: http://ez.no/ez_publish/documentation/incoming/smart_viewcache_cleaning_system Ole M. Senior Software Engineer - Vision with Technology http://www.visionwt.com http://www.omh.cc http://www.twitter.com/omh eZ Certified Developer http://ez.no/certification/verify/358441 http://ez.no/certification/verify/272578

Author

Message

Michael Zeidler

Monday 13 September 2004 3:17:27 am

Hi,

as you might have noticed according to my previous messages, I am about to optimize the response time of my ezsite using version 3.4.1 ;).
How could I avoid the clear caching when a forums entry was sent to a forum. Otherwise a new entry would initiate a publish action followed by clearing the whole template cache (equivalent to (ezsite)/bin/shell/clear-cache --clear-tpl). Of course this would make sense when you have for instance on your entry page notices about new entries in your forum.
Unfortunately you cant define dependencies about what cache-files should be deleted after a certain publish action.

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Michael Zeidler

Tuesday 14 September 2004 12:52:44 am

Maybe it is possible to determine what cache files are involved with a section. So when for instance the forum has its own section the publishing process for an forum entry could clear the cache only for this section.
To keep on dreaming it would be nice to add this section any URLs and the additional pieces of information to reproduce the cache-block key which could be used for explicit clearing from cache. This way the page in another section which shows news about forum entries could be cleared from cache too.
Btw. How is this solved on the ez.no site? I cant imagine that every forum entry clears the cache each time for the whole site?

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Ole Morten Halvorsen

Tuesday 14 September 2004 2:06:55 am

Cupic,

On publish eZ publish deletes all the ViewCache, however this bad behaviour is fixed in SVN (3.4 stable and trunk) and a new smart viewcache mechanism is added. After this fix only published nodes of the object, parent nodes and nodes of reverse related objects is cleared.

Read about it here: http://ez.no/ez_publish/documentation/incoming/smart_viewcache_cleaning_system

Ole M.

Senior Software Engineer - Vision with Technology

http://www.visionwt.com
http://www.omh.cc
http://www.twitter.com/omh

eZ Certified Developer
http://ez.no/certification/verify/358441
http://ez.no/certification/verify/272578

eZ debug

Timing:	Jan 31 2025 08:04:33
Script start
Timing:	Jan 31 2025 08:04:33
Module start 'layout'
Timing:	Jan 31 2025 08:04:33
Module start 'content'
Timing:	Jan 31 2025 08:04:33
Module end 'content'
Timing:	Jan 31 2025 08:04:33
Script end

Main resources:

Total runtime	0.0159 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	588.1484	151.2109
Module start 'layout'	0.0053	0.0021	739.3594	36.6484
Module start 'content'	0.0073	0.0073	776.0078	94.1250
Module end 'content'	0.0147	0.0012	870.1328	33.9922
Script end	0.0159		904.1250

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0021	12.9496	14	0.0001
Check MTime	0.0009	5.9046	14	0.0001
Mysql Total
Database connection	0.0008	4.7326	1	0.0008
Mysqli_queries	0.0023	14.5636	3	0.0008
Looping result	0.0000	0.0689	1	0.0000
Template Total	0.0009	5.8	1	0.0009
Template load	0.0007	4.5123	1	0.0007
Template processing	0.0002	1.2439	1	0.0002
Override
Cache load	0.0005	3.1306	1	0.0005
General
dbfile	0.0033	20.7274	8	0.0004
String conversion	0.0000	0.0510	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs