CachedViewModes question

Next topic

Author	Message
Jorge estévez	Thursday 25 December 2008 8:20:11 am Hello, I suppose that if I activate CachedViewModes not only for "full view" but for line and other personalized views I have created it will increase performance. There is a note at the documentation that says: <b>Note:Do not change this setting unless you know what you are doing.</b> So, is if ok to add line to the list of CachedViewModes? as: CachedViewModes=full;sitemap;pdf;line and so on thanks Diseño Web Cuba Web Design Cuba www.elfosdesign.com
Gaetano Giunta	Friday 26 December 2008 6:40:46 am The view cache creates one cache file per node viewed. Enabling it for line view is thus mostly useless, unless you want users to browse to the line view of content. Since by default users use only the full view mode for browsing the siten CachedViewModes has been set to only 'full'. There is no big risk in altering it, except this: when eZP clears any cached files as result of eg. publishing anew content, it will stop counting the files to be cleaned after reaching 60, and declare all the cache invalid. You just need to be sure that you do not have so many templates to be cached that you hit sixty all the time. Principal Consultant International Business Member of the Community Project Board
Jorge estévez	Friday 26 December 2008 7:57:27 am Thanks, My site uses more line views than full views as users must browser within "directories trees" to "reach" one of the nodes at the end of the tree that has products, there are 3000 or more nodes that display as line views. So I was wondering how to cache the line views to get the most of speed... I have lots of nodes displaying in line view (and lots of those nodes has as full view other bunch of nodes in line views, etc.) The limit of 60 I cannot understand. I really do not know if CachedViewModes will be good for me or not. thanks Diseño Web Cuba Web Design Cuba www.elfosdesign.com

Author

Message

Thursday 25 December 2008 8:20:11 am

Hello,

I suppose that if I activate CachedViewModes not only for "full view" but for line and other personalized views I have created it will increase performance.

There is a note at the documentation that says:

<b>Note:Do not change this setting unless you know what you are doing.</b>

So, is if ok to add line to the list of CachedViewModes? as:

CachedViewModes=full;sitemap;pdf;line and so on

thanks

Diseño Web Cuba
Web Design Cuba
www.elfosdesign.com

Gaetano Giunta

Friday 26 December 2008 6:40:46 am

The view cache creates one cache file per node viewed.

Enabling it for line view is thus mostly useless, unless you want users to browse to the line view of content.
Since by default users use only the full view mode for browsing the siten CachedViewModes has been set to only 'full'.

There is no big risk in altering it, except this:
when eZP clears any cached files as result of eg. publishing anew content, it will stop counting the files to be cleaned after reaching 60, and declare all the cache invalid.
You just need to be sure that you do not have so many templates to be cached that you hit sixty all the time.

Principal Consultant International Business
Member of the Community Project Board

Jorge estévez

Friday 26 December 2008 7:57:27 am

Thanks,

My site uses more line views than full views as users must browser within "directories trees" to "reach" one of the nodes at the end of the tree that has products, there are 3000 or more nodes that display as line views. So I was wondering how to cache the line views to get the most of speed...

I have lots of nodes displaying in line view (and lots of those nodes has as full view other bunch of nodes in line views, etc.)

The limit of 60 I cannot understand.
I really do not know if CachedViewModes will be good for me or not.

thanks

Diseño Web Cuba
Web Design Cuba
www.elfosdesign.com

eZ debug

Timing:	Jan 18 2025 15:01:25
Script start
Timing:	Jan 18 2025 15:01:25
Module start 'layout'
Timing:	Jan 18 2025 15:01:25
Module start 'content'
Timing:	Jan 18 2025 15:01:25
Module end 'content'
Timing:	Jan 18 2025 15:01:25
Script end

Main resources:

Total runtime	0.0187 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.0058	587.9141	152.6250
Module start 'layout'	0.0058	0.0048	740.5391	39.4453
Module start 'content'	0.0106	0.0065	779.9844	89.3203
Module end 'content'	0.0171	0.0016	869.3047	34.3047
Script end	0.0187		903.6094

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	12.8574	14	0.0002
Check MTime	0.0010	5.5656	14	0.0001
Mysql Total
Database connection	0.0008	4.4848	1	0.0008
Mysqli_queries	0.0042	22.4179	3	0.0014
Looping result	0.0000	0.0689	1	0.0000
Template Total	0.0013	6.7	1	0.0013
Template load	0.0007	3.6925	1	0.0007
Template processing	0.0006	2.9920	1	0.0006
Override
Cache load	0.0005	2.5365	1	0.0005
General
dbfile	0.0015	8.1850	8	0.0002
String conversion	0.0000	0.0485	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