We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 37099
    • 338 Posts
    I’ve recently been experiencing some slowness with the backend of 1.0.2.

    The front end website loads up fast enough when I load it into the browser but when I go to the backend initially it seems to hang, it takes a good few minutes to load up, the tabs and the menu bar load up quite quickly but then it seems to stall, the main right window appears first but the document tree on the left quite often shows just the root node and says "This container is empty" underneath. I click the "Refresh Site Tree" button and the pages appear. Everything seems to work OK after that, it seems to just be the initial loading.

    This is worrying as I think it will give a bad impression to clients who have backend logins.

    I’ve never had it happen with 1.0.2.

    Any suggestions?

    Thanks
    Mike
      • 25663 MODX Staff
      • 12,272 Posts
      Check to see if you have a lot of entries in the manager log or system events. Will be interesting to know. System events may indicate a problem, and big manager logs can cause things to slow down.
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 37099
        • 338 Posts
        Quote from: rthrash at Mar 21, 2010, 08:20 AM

        Check to see if you have a lot of entries in the manager log or system events. Will be interesting to know. System events may indicate a problem, and big manager logs can cause things to slow down.

        Thanks for responding.

        No, nothing at all in the system events log; there were 340 entries in the manager logs which I cleared. Logged out and then logged in again, same thing: took about 2 minutes to load, and had to refresh the document tree to see anything. The front end still works fine.

        Mike
          • 37099
          • 338 Posts
          I think it might be something to do with the server its on, I have 2 copies of 1.0.2 and one copy of 1.0.1 on the same server and they all show this sluggishness when starting but I have 0.9.6 and 1.0.1 on another server and they are just fine.

          Any ideas what I should look for on this particular server that might be slowing down the manager start up?

          Mike
            • 1343 ☆ A M B ☆
            • 2,213 Posts
            You could try putting this in your template:

            Time [^qt^] Queries [^q^] PHP time [^p^] Total Time [^t^] Source of Load [^s^]

            It should help track down the issue.
              Patrick | Server Wrangler
              About Me: Website | Tweets |  MODX Hosting
              • 25663 MODX Staff
              • 12,272 Posts
              Also clear the entries for the RSS feeds for the announcements and the security feeds. I suspect there may be some proxy-fu going on.
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 37099
                • 338 Posts
                Quote from: rthrash at Mar 22, 2010, 08:04 AM

                Also clear the entries for the RSS feeds for the announcements and the security feeds. I suspect there may be some proxy-fu going on.

                YAY grin

                That was it, I cleared the RSS feeds and the manager loads up instantly again smiley That’s going to be a lot better for the client backend user experience.

                Thanks for your help and suggestions.

                I wonder why it started doing that? It was most disconcerting.

                Mike
                  • 25663 MODX Staff
                  • 12,272 Posts
                  A proxy or firewall can block connections to those feeds and create the slowdowns. Essentially, it has to timeout to continue loading creating the perception of a slowdown. Their network admin can probably open them back up.
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me