We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 9207 ☆ A M B ☆
    • 2,475 Posts
    How much memory did you allocate? I recently saw a Revo site with 1024MB allocated to PHP, and the manager was still sluggish. There were other problems with the host (e.g. the box only had 1GB of RAM to begin with), but how much memory did your site need?
      • 32699 ☆ A M B ☆
      • 427 Posts
      I gave it 2GB and then decided I was going to play smart guy and replaced ALL of those pages with apache doing the lifting and 4 revo resources doing the catching.

      I am now back to 64 megs, but hardly touch it.
        Get your copy of MODX Revolution Building the Web Your Way http://www.sanitypress.com/books/modx-revolution-building-the-web-your-way.html

        Check out my MODX || xPDO resources here: http://www.shawnwilkerson.com
        • 9207 ☆ A M B ☆
        • 2,475 Posts
        Can you clarify? You have Apache doing the lifting? Do you mean you somehow exported those pages to static text? Or that you restructured your site to it relied on 4 MODx resources instead of hundreds of resources?

        This seems to be a common theme though... it seems that having too many MODx resources requires a lot of PHP memory... the solutions that favor using fewer resources seem to be the faster ones.
          • 14349
          • 44 Posts
          I guess for large product driven sites - individual resources might not be the way to go -

          So if I were to build a site like this again, I would create some custom database tables and just have a manager component were one could change product fields/data.

          So it would be database driven without using resources - so as not to confuddle the manager.
            • 14349
            • 44 Posts
            Update:

            I wrote that snippet described above which automatically grabs every 1000 products and sticks them into a "folder" container. This solves the problem for now.

            Looks like EXTj / Modx can handle up to 1000 resources (give or take a hundred) - at least on my servers.

            If you have a large Resource driven modx site please feel free to post 1. How many resources it takes to crash the manager for you 2. your system specs (check your php mem limit) 3. Any javascript errors
            4. and what you have done to get past the problem
              • 19388
              • 297 Posts
              It is a bit ironic, now that MODx supports more than 5.000 documents, there is something that puts new limits sad
                • 9207 ☆ A M B ☆
                • 2,475 Posts
                Agreed... this is ironic: the front-end now handles thousands of resources, but the manager has difficulties. I suspect that the devs are fully aware of this and working to smooth things out.
                  • 14349
                  • 44 Posts
                  revo 2.0.7 has done an excellent job.

                  I have over 20,000 resources (whooooo) and the manager is lighting fast (I also have the javascript cache on for the manager tree)

                  This is a full ecommerce site with traffic so hats off to the modx team.
                    • 9207 ☆ A M B ☆
                    • 2,475 Posts
                    Nice! That’s really good to know. Thanks for sharing.
                      • 28042 ☆ A M B ☆
                      • 24,524 Posts
                      Hmm. Maybe the Manager optimization will make it run less like an arthritic granny on my poor overworked iBook.
                        Studying MODX in the desert - http://sottwell.com
                        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                        Join the Slack Community - http://modx.org