Performant Storage Engine

This feature request is part of Community Roadmap

Description

With the new persistence interface it will be possible to develop sophisticated storage engines which can handle large amounts of objects.

Possible candidates:

Tags:

Participants:

eZ debug

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	588.0703	152.6406
Module start 'layout'	0.0050	0.0048	740.7109	39.4844
Module start 'content'	0.0097	0.0059	780.1953	95.1797
Module end 'content'	0.0157	0.0025	875.3750	30.2891
Script end	0.0182		905.6641

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	13.7554	14	0.0002
Check MTime	0.0012	6.6833	14	0.0001
Mysql Total
Database connection	0.0006	3.4595	1	0.0006
Mysqli_queries	0.0042	23.2853	3	0.0014
Looping result	0.0000	0.1755	1	0.0000
Template Total	0.0021	11.6	1	0.0021
Template load	0.0012	6.6296	1	0.0012
Template processing	0.0009	4.8933	1	0.0009
Override
Cache load	0.0006	3.4372	1	0.0006
General
dbfile	0.0011	6.0796	8	0.0001
String conversion	0.0000	0.0484	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

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