Resources tree too slow?

Hi,
I’m developing a site that have ( by the moment ) around 70 documents structured in a 6 levels depth tree

level 1
- level 2
- - level 3
- - - level 4
- - - - level 5
- - - - - level 6

Each time I click to edit or save a document, all the page is refreshed and the tree is regenerated again to focus the actual resource being edited. But it take some seconds refreshing each parent/childs. It shows a "loading" animation for each one of the 6 elements if i’m editing an element in level 6... I think it should be improved.
Someone with the same problem?

Refer to my post here http://modxcms.com/forums/index.php/topic,53535.msg310548.html

Check your php memory limit settings - maybe your host is putting a hold on how many queries mysql can call per hour.


Please post your server specs too : )

I’ll try to increase memory, thanks.

PHP Version 5.2.14
LiteSpeed V5.4
MySQL 5.0.91
(shared hosting)
Intel(R) Xeon(R) CPU 5130 @ 2.00GHz
Memory: 4145656k/4980736k available (2176k kernel code, 46624k reserved, 901k data, 228k init, 3276160k highmem)
Linux 2.6.18-194.11.3.el5PAE #1 SMP i686 i686 i386 GNU/Linux

I have a problem I’m solving now with sysadmins, while they do it I was thinking... I think ( i’m not sure! ) the tree childs are requested each time we click an element. Won’t be a better idea to get the entire tree in the first load and have it cached? Something could be developed to refresh the tree only if needed or refresh it on request. I hate it but, TYPO3 do it.

I increased the memory limit to 1024M but the problem persists. It looks like if connections are being done by levels, doing a connection for each level. But I haven’t seen the code, i’m only looking what visually happens. Here is a link to a video to see what is happening.
http://www.youtube.com/watch?v=lO9SNp0HbRg

Quote from: mIDO at Sep 07, 2010, 04:24 AM

I have a problem I’m solving now with sysadmins, while they do it I was thinking... I think ( i’m not sure! ) the tree childs are requested each time we click an element. Won’t be a better idea to get the entire tree in the first load and have it cached? Something could be developed to refresh the tree only if needed or refresh it on request. I hate it but, TYPO3 do it.

This approach doesn’t scale at all with sites above 1000 pages; the amount of memory needed to load the nodes would be astronomical. Doing asynchronous node loading is the only way of doing a tree view that will scale.

If you’re bothered by the depth loading, you could use Quick Update and Quick Create more, as those actions allow you to edit Resources/Elements without having to reload the page.

Quick update/Quick create is a patch. Everytime we need to reload page or tree, the tree needs a lot of time to be completely expanded. I really think it must be solved anyway and I really believe it can be done...

Finally I posted this as a bug but it seems not to be a bug but... a problem in my server? another kind of problem? am I the only one with this issue???
All the information is here: http://bugs.modx.com/issues/2510

Have you tried turning on the cache_database option to see if this significantly improves the performance?

I have enabled it, cleared cache, cleared browser cache. Tried it in Chrome and Firefox and the result is the same. The right zone is loaded firstly and then, once it has finished loading, the tree start loading child by child.