Number of nodes per parent node vs. performance

Previous topic

Developer

Next topic

Author	Message
Piotrek Karaś	Thursday 03 July 2008 1:01:33 pm Hi there, I'm planning the information structure for one of our projects, and it seems that actually flat structure may be one of the best options. And here's the question: <b>how many child nodes under one parent node can eZ Publish handle without serious performance issues?</b> I do not require all operations, though. All I need is that I can access the full view of each of those child nodes as well as getting all the nodes indexed for search purposes. This parent container will not provide any listing or fetching of all of its child elements. Thanks, Piotrek EDIT: I think I should have put it here: http://ez.no/developer/forum/setup_design/unbelievably_slow_query/re_unbelievably_slow_query__12 -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Piotrek Karaś

Thursday 03 July 2008 1:01:33 pm

Hi there,

I'm planning the information structure for one of our projects, and it seems that actually flat structure may be one of the best options. And here's the question: <b>how many child nodes under one parent node can eZ Publish handle without serious performance issues?</b>

I do not require all operations, though. All I need is that I can access the full view of each of those child nodes as well as getting all the nodes indexed for search purposes. This parent container will not provide any listing or fetching of all of its child elements.

Thanks,
Piotrek

EDIT: I think I should have put it here:
http://ez.no/developer/forum/setup_design/unbelievably_slow_query/re_unbelievably_slow_query__12

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

eZ debug

Timing:	Jan 20 2025 14:34:09
Script start
Timing:	Jan 20 2025 14:34:09
Module start 'layout'
Timing:	Jan 20 2025 14:34:09
Module start 'content'
Timing:	Jan 20 2025 14:34:09
Module end 'content'
Timing:	Jan 20 2025 14:34:09
Script end

Main resources:

Total runtime	0.0218 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.0079	590.2813	152.6406
Module start 'layout'	0.0079	0.0046	742.9219	39.4766
Module start 'content'	0.0125	0.0072	782.3984	89.3672
Module end 'content'	0.0196	0.0021	871.7656	30.3047
Script end	0.0218		902.0703

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	14.6590	14	0.0002
Check MTime	0.0015	6.7514	14	0.0001
Mysql Total
Database connection	0.0012	5.4127	1	0.0012
Mysqli_queries	0.0042	19.3340	3	0.0014
Looping result	0.0001	0.2656	1	0.0001
Template Total	0.0017	7.9	1	0.0017
Template load	0.0009	4.0248	1	0.0009
Template processing	0.0008	3.7997	1	0.0008
Override
Cache load	0.0006	2.8052	1	0.0006
General
dbfile	0.0013	5.7788	8	0.0002
String conversion	0.0000	0.0535	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