eZDFS cache management

Next topic

Author	Message
Matthieu Sévère	Thursday 07 January 2010 6:32:46 am Hello :-) I've never installed eZ Publish in eZDFS mode but I am wondering on the cache is managed : Considering that the cache is stored locally on each front, when you edit an object for example : how the cache is cleaned for this object on each front ? Thank you :-) -- eZ certified developer: http://ez.no/certification/verify/346216
Nicolas Pastorino	Thursday 07 January 2010 6:36:53 am I think so : http://share.ez.no/forums/install-configuration/ezdfsfilehandler#comment55719 Cheers ! -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
Bertrand Dunogier	Thursday 07 January 2010 6:45:54 am Based on your twitter response, it seems that the other thread doesn't explain that completely. It is actually quite simple: the central repository for cache when using eZDFS is NFS (by default) + the ezdfsfile cluster table. The table is used to check the actual mtime, validity, etc. When a cache item is cleared, it is marked as expired in this table. When it gets regenerated, the item's mtime is modified in the table as well. Any other server of the cluster that further requests this cache file will compare its mtime in the DB to the local cache file's mtime. So as soon as a cache item's mtime is changed in the DB, any local version older than this mtime will be replaced with the updated file. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Matthieu Sévère	Thursday 07 January 2010 7:11:11 am Thank you for your answer I understand know. In fact, I misunderstood your first topic because I thought that locally means out of NFS. And, if it is in NFS everything is clear :-) Actually I asked this question because I have a ezpublish running on 3 servers : 2 fronts and one back. There is a main database on the back and everything else is shared with NFS. But, NFS is really slow and generating the cache is taking like more than 2s each time! So I moved the cache folder out of NFS (so what I call locally :-) ) but know I have to deal with clearing the cache on each server .... I'm not sure it's the good solution though ... Thanks for your reply :-) -- eZ certified developer: http://ez.no/certification/verify/346216
Bertrand Dunogier	Thursday 07 January 2010 7:17:37 am NFS alone shouldn't make things THAT slow. It is bad, but not that much when it comes to speed. In eZDFS, we chose to consider NFS as a simple files repository, and completely ignore it when it comes to metadata & concurrency handling (this is done using the database, as we have complete control over what the DB does). Keep in mind that you will have a small loss of performances if you use eZDFS (usually around -10% page views), but cache updates will be completely transparent. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Matthieu Sévère	Thursday 07 January 2010 7:23:28 am Ok, so maybe there is something else that slows NFS. Thanks for your help, it's been usefull ! -- eZ certified developer: http://ez.no/certification/verify/346216

eZ debug

Timing:	Jan 18 2025 02:07:44
Script start
Timing:	Jan 18 2025 02:07:44
Module start 'layout'
Timing:	Jan 18 2025 02:07:44
Module start 'content'
Timing:	Jan 18 2025 02:07:45
Module end 'content'
Timing:	Jan 18 2025 02:07:45
Script end

Main resources:

Total runtime	0.5947 sec
Peak memory usage	4,096.0000 KB
Database Queries	69

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0063	587.9219	152.6250
Module start 'layout'	0.0063	0.0038	740.5469	39.4609
Module start 'content'	0.0101	0.5831	780.0078	630.0313
Module end 'content'	0.5932	0.0014	1,410.0391	16.1719
Script end	0.5946		1,426.2109

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0037	0.6279	16	0.0002
Check MTime	0.0015	0.2462	16	0.0001
Mysql Total
Database connection	0.0012	0.2092	1	0.0012
Mysqli_queries	0.5275	88.7061	69	0.0076
Looping result	0.0007	0.1210	67	0.0000
Template Total	0.5644	94.9	2	0.2822
Template load	0.0024	0.4083	2	0.0012
Template processing	0.5619	94.4973	2	0.2810
Template load and register function	0.0001	0.0197	1	0.0001
states
state_id_array	0.0010	0.1618	1	0.0010
state_identifier_array	0.0007	0.1232	2	0.0004
Override
Cache load	0.0020	0.3329	35	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1160	3	0.0002
Fetch class attribute name	0.0011	0.1904	9	0.0001
XML
Image XML parsing	0.0015	0.2495	3	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0031	12	0.0000
General
dbfile	0.0012	0.1976	28	0.0000
String conversion	0.0000	0.0016	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
6	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 22 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs