Forums / Developer / Number of nodes per parent node vs. performance

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

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 Exponential 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