ezcontentcache and ini variables.

Previous topic

Developer

Next topic

Author	Message
Chris Williams	Friday 12 November 2010 4:27:29 am I was advised to look at "ezcontentcache" to start my research into understanding how caching is done in eZ. ./kernel/classes/ezcontentcache.php On line 291, the following comments are written. // Figure out the siteaccess which are related, first using the new // INI setting RelatedSiteAccessList then the old existing one // AvailableSiteAccessList Firstly, thank you for the comments, it makes it so much easier for other developers to understand what was the aim. Please let it continue. This topic is based on those very comments. If you read the rest of the code in that method, you will see that it actually uses "RelatedSiteAccessList" if it exists and skips "AvailableSiteAccessList". I read it, that it should try "RelatedSiteAccessList" then use "AvailableSiteAccessList", I further believe it should be like this, after I did a search of ez directory via the command line to discover the use of"AvailableSiteAccessList" in 4.4. I would have made an issue about this, but im aware issues.ez.no are not the most read by others. Equally, I had a peak into site.ini and there is no mention that it is the preffered ini setting variable, which again to me makes it more important to check both.
André R.	Friday 12 November 2010 5:37:56 am RelatedSiteAccessList and AvailableSiteAccessList are different setting, the first is a list of site accesses that are related to current site access, share db for instance, share content on multi side setup and so on. The latter is list of all available site accesses on the eZ Publish installation. So they are not interchangable, the reason eZContentCache fallbacks to AvailableSiteAccessList is that RelatedSiteAccessList was added in 3.8 or 3.9 and fallback for existing setups where provided for bc (backward compatibility) at the time. Code written after that mostly use one or the other depending on use. So eZContentCache should be cleaned up to only use RelatedSiteAccessList imho. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom

Author

Message

Chris Williams

Friday 12 November 2010 4:27:29 am

I was advised to look at "ezcontentcache" to start my research into understanding how caching is done in eZ.

./kernel/classes/ezcontentcache.php

On line 291, the following comments are written.

// Figure out the siteaccess which are related, first using the new
// INI setting RelatedSiteAccessList then the old existing one
// AvailableSiteAccessList

Firstly, thank you for the comments, it makes it so much easier for other developers to understand what was the aim. Please let it continue.

This topic is based on those very comments.

If you read the rest of the code in that method, you will see that it actually uses "RelatedSiteAccessList" if it exists and skips "AvailableSiteAccessList".

I read it, that it should try "RelatedSiteAccessList" then use "AvailableSiteAccessList", I further believe it should be like this, after I did a search of ez directory via the command line to discover the use of"AvailableSiteAccessList" in 4.4.

I would have made an issue about this, but im aware issues.ez.no are not the most read by others.

Equally, I had a peak into site.ini and there is no mention that it is the preffered ini setting variable, which again to me makes it more important to check both.

André R.

Friday 12 November 2010 5:37:56 am

RelatedSiteAccessList and AvailableSiteAccessList are different setting, the first is a list of site accesses that are related to current site access, share db for instance, share content on multi side setup and so on. The latter is list of all available site accesses on the eZ Publish installation.

So they are not interchangable, the reason eZContentCache fallbacks to AvailableSiteAccessList is that RelatedSiteAccessList was added in 3.8 or 3.9 and fallback for existing setups where provided for bc (backward compatibility) at the time. Code written after that mostly use one or the other depending on use.

So eZContentCache should be cleaned up to only use RelatedSiteAccessList imho.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

eZ debug

Timing:	Jan 18 2025 04:13:41
Script start
Timing:	Jan 18 2025 04:13:41
Module start 'layout'
Timing:	Jan 18 2025 04:13:41
Module start 'content'
Timing:	Jan 18 2025 04:13:42
Module end 'content'
Timing:	Jan 18 2025 04:13:42
Script end

Main resources:

Total runtime	0.9842 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	591.5547	152.6250
Module start 'layout'	0.0052	0.0031	744.1797	39.4531
Module start 'content'	0.0083	0.9744	783.6328	529.7656
Module end 'content'	0.9827	0.0014	1,313.3984	12.1563
Script end	0.9841		1,325.5547

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.3063	16	0.0002
Check MTime	0.0013	0.1289	16	0.0001
Mysql Total
Database connection	0.0009	0.0913	1	0.0009
Mysqli_queries	0.9389	95.4058	54	0.0174
Looping result	0.0005	0.0489	52	0.0000
Template Total	0.9583	97.4	2	0.4791
Template load	0.0018	0.1820	2	0.0009
Template processing	0.9565	97.1877	2	0.4782
Template load and register function	0.0002	0.0229	1	0.0002
states
state_id_array	0.0006	0.0657	1	0.0006
state_identifier_array	0.0007	0.0725	2	0.0004
Override
Cache load	0.0014	0.1433	24	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.0895	2	0.0004
Fetch class attribute name	0.0022	0.2205	3	0.0007
XML
Image XML parsing	0.0006	0.0654	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0013	3	0.0000
General
dbfile	0.0008	0.0773	17	0.0000
String conversion	0.0000	0.0010	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/strong.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/strong.tpl
3	content/datatype/view/ezxmltags/emphasize.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/emphasize.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 8

Time used to render debug report: 0.0001 secs