Use some cache in a custom fetch function

Next topic

Author	Message
Jerome Despatis	Thursday 01 April 2010 10:08:57 am Hi, I've done a function fetch in my extension, It may be called several times in a page, and I now the result is always the same, how can I make my fetch use a cache ? I could use $GLOBALS of course and store in a specific key (hoping not to override an existing key), but I'm sure there's a better way :) Any idea is welcome
Bertrand Dunogier	Thursday 01 April 2010 12:06:11 pm Well, honestly, if you just need to cache temporary data for one run, you should use a global... just centralize the read/write code for these globals so that you can easily refactor it, and prefix your global names with your initials or company acronym... just like we do with eZ. There should be no conflicts this way (not more than with classes, at least :p). If you want to implement more persistent caching, here are the options I would consider: ezcCache. That's it :p We plan on re-implementing most caches using the Cache component from the ezComponents. It has support for hierarchical cache, and already supports standard backends (memcache, APC, files...). http://ezcomponents.org/docs/tutorials/Cache Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Jerome Despatis	Thursday 01 April 2010 12:34:28 pm Ok thanks I already use it for plain file cache, I've seen memory cache also, let's test that...

Author

Message

Thursday 01 April 2010 10:08:57 am

Hi,

I've done a function fetch in my extension, It may be called several times in a page, and I now the result is always the same, how can I make my fetch use a cache ?

I could use $GLOBALS of course and store in a specific key (hoping not to override an existing key), but I'm sure there's a better way :)

Any idea is welcome

Bertrand Dunogier

Thursday 01 April 2010 12:06:11 pm

Well, honestly, if you just need to cache temporary data for one run, you should use a global... just centralize the read/write code for these globals so that you can easily refactor it, and prefix your global names with your initials or company acronym... just like we do with eZ. There should be no conflicts this way (not more than with classes, at least :p).

If you want to implement more persistent caching, here are the options I would consider:

ezcCache. That's it :p
We plan on re-implementing most caches using the Cache component from the ezComponents. It has support for hierarchical cache, and already supports standard backends (memcache, APC, files...).
http://ezcomponents.org/docs/tutorials/Cache

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

Jerome Despatis

Thursday 01 April 2010 12:34:28 pm

Ok thanks

I already use it for plain file cache, I've seen memory cache also, let's test that...

eZ debug

Timing:	Jan 18 2025 02:56:02
Script start
Timing:	Jan 18 2025 02:56:02
Module start 'layout'
Timing:	Jan 18 2025 02:56:02
Module start 'content'
Timing:	Jan 18 2025 02:56:03
Module end 'content'
Timing:	Jan 18 2025 02:56:03
Script end

Main resources:

Total runtime	0.7580 sec
Peak memory usage	4,096.0000 KB
Database Queries	58

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0069	589.1641	152.6406
Module start 'layout'	0.0069	0.0039	741.8047	39.4766
Module start 'content'	0.0108	0.7459	781.2813	536.2031
Module end 'content'	0.7567	0.0013	1,317.4844	12.1250
Script end	0.7580		1,329.6094

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.4455	16	0.0002
Check MTime	0.0013	0.1738	16	0.0001
Mysql Total
Database connection	0.0012	0.1574	1	0.0012
Mysqli_queries	0.7060	93.1361	58	0.0122
Looping result	0.0012	0.1563	56	0.0000
Template Total	0.7125	94.0	2	0.3563
Template load	0.0026	0.3425	2	0.0013
Template processing	0.7099	93.6564	2	0.3550
Template load and register function	0.0001	0.0181	1	0.0001
states
state_id_array	0.0018	0.2348	1	0.0018
state_identifier_array	0.0013	0.1749	2	0.0007
Override
Cache load	0.0023	0.2986	21	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0685	2	0.0003
Fetch class attribute name	0.0009	0.1148	4	0.0002
XML
Image XML parsing	0.0025	0.3294	2	0.0012
class_abstraction
Instantiating content class attribute	0.0000	0.0014	4	0.0000
General
dbfile	0.0032	0.4164	16	0.0002
String conversion	0.0000	0.0015	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	content/datatype/view/ezxmltags/li.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/li.tpl
1	content/datatype/view/ezxmltags/ul.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/ul.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 9

Time used to render debug report: 0.0001 secs