generated pages

Previous topic

General

Next topic

Author	Message
Francesco Sottile	Tuesday 05 April 2005 3:01:43 am Hi all, i would like to know if eZ Publish generates normal html pages from the given content or if it uses a caching system. tnx
Kristian Hole	Tuesday 05 April 2005 11:00:56 am I'm not exactly sure what you're asking, but i'll try to answer anyway. eZ publish generates html from the content objects stored in the database. This html generation takes some time, and is not always needed (if the content does not change). That is why the generated html often is cached, and this pregenerated cache used instead of rendering it fully each time. So the answer is: yes, both. If you wonder if its possible to turn this of, then offcourse it is. This is useful when developing pages (but dead slow on production sites). This page shows you how to turn off template caching (and to show which templates is being used for generating the page) http://ez.no/ez_publish/documentation/customization/tips_tricks/show_which_templates_are_used I hope this was helpful. Kristian http://ez.no/ez_publish/documenta...tricks/show_which_templates_are_used http://ez.no/doc/ez_publish/techn...te_operators/miscellaneous/attribute
Francesco Sottile	Wednesday 06 April 2005 3:36:37 am Tnx Kristian, that is exactly what i needed to know. :)

Author

Message

Francesco Sottile

Tuesday 05 April 2005 3:01:43 am

Hi all,

i would like to know if eZ Publish generates normal html pages from the given content or if it uses a caching system.

tnx

Kristian Hole

Tuesday 05 April 2005 11:00:56 am

I'm not exactly sure what you're asking, but i'll try to answer anyway. eZ publish generates html from the content objects stored in the database. This html generation takes some time, and is not always needed (if the content does not change). That is why the generated html often is cached, and this pregenerated cache used instead of rendering it fully each time. So the answer is: yes, both.

If you wonder if its possible to turn this of, then offcourse it is. This is useful when developing pages (but dead slow on production sites).

This page shows you how to turn off template caching (and to show which templates is being used for generating the page)
http://ez.no/ez_publish/documentation/customization/tips_tricks/show_which_templates_are_used

I hope this was helpful.

Kristian

http://ez.no/ez_publish/documenta...tricks/show_which_templates_are_used
http://ez.no/doc/ez_publish/techn...te_operators/miscellaneous/attribute

Francesco Sottile

Wednesday 06 April 2005 3:36:37 am

Tnx Kristian, that is exactly what i needed to know.

eZ debug

Timing:	Jan 18 2025 15:09:23
Script start
Timing:	Jan 18 2025 15:09:23
Module start 'layout'
Timing:	Jan 18 2025 15:09:23
Module start 'content'
Timing:	Jan 18 2025 15:09:23
Module end 'content'
Timing:	Jan 18 2025 15:09:23
Script end

Main resources:

Total runtime	0.0154 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.0060	588.8984	152.6094
Module start 'layout'	0.0060	0.0030	741.5078	39.3984
Module start 'content'	0.0089	0.0048	780.9063	89.2578
Module end 'content'	0.0137	0.0016	870.1641	34.3047
Script end	0.0153		904.4688

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	16.2843	14	0.0002
Check MTime	0.0012	7.6801	14	0.0001
Mysql Total
Database connection	0.0008	5.4328	1	0.0008
Mysqli_queries	0.0031	20.4544	3	0.0010
Looping result	0.0000	0.1041	1	0.0000
Template Total	0.0013	8.7	1	0.0013
Template load	0.0007	4.5801	1	0.0007
Template processing	0.0006	4.1437	1	0.0006
Override
Cache load	0.0005	3.2507	1	0.0005
General
dbfile	0.0012	7.9162	8	0.0002
String conversion	0.0000	0.0388	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