3.5 with large site?

Next topic

Author	Message
Marco Zinn	Thursday 04 November 2004 3:28:29 pm Hi, as the beta is out, a quick question: The content-structure menu seems to be made of a collapsable treemenu, made with JS, i guess. One note (i think, from the alpha release) was, that this is "not optimized for large sites". From my understanding, the current "collapsable treemenu approach" (which i like in terms of usability) requires at least to have the names of all nodes below the "content root" node to be in "the" HTML code (or some external JS code, but it must be created, stored, (cached) and transmitted anyway). Correct? Does anyone have some first impressions for a "large site". "Large" means: 500+ folders 1500+ articles 2000+ files So, this could sum up to approx. 4000 nodes, which must be "prepared" for the content structure. Marco http://www.hyperroad-design.com
Balazs Halasy	Friday 05 November 2004 12:11:12 am Hi, The treemenu has been optimized a lot since the initial version. However, it was not designed to cope with too many nodes. That is why you have the possibility to turn it off and/or tweak it so that it only shows specific type of nodes. In addition, you can also limit it to only get a certain number of nodes and/or to only go to a certain depth within the node-tree. If you have a fast server and a fast connection: sure, it will probably work with a lot of nodes. If not: tweak/limit or or turn it off. :-) Allman
Daniele P.	Monday 08 November 2004 12:23:01 am For the large output use mod_deflate to compress the page. I posted a suggestion and some test: http://ez.no/community/bug_reports/missing_doc_about_mod_deflate
Marco Zinn	Thursday 11 November 2004 7:08:51 am Thanks for the hint! We're in some intranet, which usually has enough bandwith. I am more concerned about the DB queries, than about the HTML file size, that results, but any compression should help here, too. Marco http://www.hyperroad-design.com