Resources Tree Very Slow

I'm running MODX Revolution 2.2.9-pl (traditional) and the resources tree is killing me! It takes a very long time to load every time I do something in MODX. Is there a cache setting for it so it can load faster? My internet connection is zippy and the rest of MODX seems to run quickly but the resources tree is very frustrating.

Quote from: mikegrace at Dec 05, 2013, 08:54 AM

I'm running MODX Revolution 2.2.9-pl (traditional) and the resources tree is killing me! It takes a very long time to load every time I do something in MODX. Is there a cache setting for it so it can load faster? My internet connection is zippy and the rest of MODX seems to run quickly but the resources tree is very frustrating.

Out of curiosity how many resources are there? There are a few experimental cache settings but I am not sure if they affect the tree.

We are almost to 300 resources.

I'm having this issue as well; navigating the resource tree is particularly slow, and switching between resources/elements is also slow.

What's interesting is that a few people who work on the site are using Windows and a few are using Mac; those using Windows have faster load times than those on OSX.

Any ideas?

In my opinion, this problem is endemic with the tree... we need something that can display larger numbers of items. The tree is perfect for displaying smallish numbers of resources, but it fails when the number of resources outdoes the RAM available on the server...

The problem is endemic of the tree. With addition of the uberbar in 2.3 I think we will alleviate users from having to use the trees as often to do things like search for resources or elements. Anyone seen the new tree in TextMate 2. I really like how you can double click folders to "zoom into" them and make them the top level node (rather than just opening them). This allows you to open each folder basically as it's own tree:

I haven't looked at 2.3 yet, but yeah... basically there are times when you need to see a whole "leaf", and times when you need to paginate large result sets. The TextMate2 solution is a good one... I was working on a custom resource class (CRC) for Revo that would act like an articles container: it wouldn't display its contents in the main tree, but instead it shows a paginated list of them. Unlike the articles container, however, it's allows any resources to be placed into it (not just articles). That type of solution is what the OP needs, I think...

The uberbar sounds like a nice addition. Look forward to trying it soon.

My client is complaining that the mananger is really slow, and I suspect this has something to do with the resource tree. It is not to bad at my side, but then I'm using windows and they are using mac. It might have been improved with the revo 2.2.11, but to early to say.

It may be worth examining your server... are you on a shared server (e.g. cPanel)? Or do you have your own VPS? How much memory do you have?