We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Is the manager slow for anyone else in MODx Revolution 2.0.0-beta-1?

    • 28215
    • 4,149 Posts
    splittingred Reply #41, 17 years, 4 months ago
    Quote from: richardtmorgan at Jun 08, 2009, 02:50 AM

    I’m also finding the manager too slow (several seconds to expand the resources tree on the left; several seconds to populate a select input). It’s makes the Evolution manager easier to use (though not as beautiful, slick or generally awesome). Hopefully some js optimisation will help.

    No chance of an ajax/oldschool compromise where the resource tree and select boxes are pre-populated and ajax updating is only invoked when something changes?

    You really shouldn’t be having response times that slow; check your apache/php logs to make sure something’s not failing. What server environment are you running on? Is this a remote host? What’s your bandwidth? Browser/OS?
      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
      • 12512
      • 42 Posts
      hwmaier Reply #42, 17 years, 4 months ago
      I already posted about this issue here:

      http://modxcms.com/forums/index.php/topic,36294.0

      and now while reading this post see that quite a few people are sharing the same experience. Most of these people run Firefox without Firebug enabled and also on a local machine, so we are looking at an issue which is not impacted by network bandwith rather than Javascript processing power.

      I understand that the release is beta and therefore this slow redraw issue can be tolerated. However for a broader acceptance of Modx, I suggest it to be investigated an fixed or improved.
        • 28215
        • 4,149 Posts
        splittingred Reply #43, 17 years, 4 months ago
        Quote from: hwmaier at Jun 08, 2009, 11:21 PM

        I already posted about this issue here:
        http://modxcms.com/forums/index.php/topic,36294.0
        and now while reading this post see that quite a few people are sharing the same experience. Most of these people run Firefox without Firebug enabled and also on a local machine, so we are looking at an issue which is not impacted by network bandwith rather than Javascript processing power.
        Right, and we’re debugging and testing on local machines as well, and not getting near the delays you are reporting.


        I understand that the release is beta and therefore this slow redraw issue can be tolerated. However for a broader acceptance of Modx, I suggest it to be investigated an fixed or improved.
        While we are working at improvements, there are a few considerations that need to be made:

        1. I have asked those having delays for environment information, as well as any Apache/PHP error messages that might be related to the delay. I am still waiting on that information, as none of those getting delays have provided it.
        2. There is a *lot* more going on in the Revo manager than the Evo manager. Plus, you’re not reloading pages, so proportionally the page loads are the same time, if not faster than, 0.9.6.
        3. The JS is not compressed yet. That will be done for GA, and possibly RCs.
        4. While it looks like a native application, it is not. It is still bound to Javascript, and each browser’s implementation and efficiency in using it.

        If you have suggestions on improving the speed, we’re all ears. Otherwise please provide more detailed information about your server environment, logs, errors, and testing.
          shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
          • 38755
          • 43 Posts
          protocreate Reply #44, 17 years, 4 months ago
          Ok, seems this could use repeating: I am using Firefox, to a web based host (so this is with latency), and I’m not experiencing any untoward speed impact (I haven’t had a chance to compare directly to Chrome). Response isn’t laggy, on par with similarly complex applications (google apps for example).

          Why should my Firefox experience be different? I’m using the Firefox 3.5 beta with the newer Tracemonkey javascript engine enabled. I suggest if anyone is going to report performance issues that they specify the version of Firefox and whether Tracemonkey is enabled or not... these reports are subjective enough already without info about environment, platform, and such info. With better metrics it would be clearer if there really is anything that should be optimized or if things are performing at the level that can be expected for the complexity of the application.

          Edit: Ninja’d with much better info from Shaun  wink  So, the take away for this post -- performance is not an issue and within what can be expected for my machine’s performance and connection speed, under the following conditions:

          - Firefox 3.5 beta
          -- Newer tracemonkey javascript engine enabled
          - Connecting to Revo on a standard shared LAMP host
          - 25 or so extensions loaded (anybody having performaince issues should make sure to test with a clean profile... extensions can be responsible for all kinds of FF performance issues), including Firebug (suspended but enabled as an extension)
          - Not experiencing issues so nothing in logs / errors etc to report
            • 12512
            • 42 Posts
            hwmaier Reply #45, 17 years, 4 months ago
            Quote from: splittingred at Jun 08, 2009, 11:26 PM


            If you have suggestions on improving the speed, we’re all ears. Otherwise please provide more detailed information about your server environment, logs, errors, and testing.

            I also saw the other posts of people reporting acceptable performance. So I also started to wonder what does distinguish these two groups in terms of server configuration and client machine?

            Here is a spec of my environment:
            a) Server environment:
            Intel Core 2 1.8GHz
            2 GB RAM
            Windows XP SP3
            WAMPServer 2.0h running:
            - MySQL 5.1.33
            - PHP 5.2.9-2
            - Apache 2.2.11
            - Antivirus/Internet security app: AVG 8.5, but disabled to avoid interference
            - Log files: No error entries for PHP, mySQL or httpd
            b) Client environment
            Any of these 3 browsers have the slow redraw effect for the document tree panel:
            - Firefox 3.0.5
            - Google chrome (despite reports by others no improvement)
            - IE7
            c) Network
            Running modx on localhost interface

            Is there anything else I should look at and report?

            Is there an easy way to enable the Javascript compression?
              • 28215
              • 4,149 Posts
              splittingred Reply #46, 17 years, 4 months ago
              Quote from: hwmaier at Jun 09, 2009, 12:01 AM

              Is there anything else I should look at and report?
              Your specs look fine. The only other thing I can think of is to check and see if there’s any wayward errors in modx/core/cache/error.log that might be related, or if there’s any JS errors in the browser.

              I’ll look more into your server specs tomorrow.

              Is there an easy way to enable the Javascript compression?

              Not at the moment - we’ve been working on a System Setting to toggle it (it’s actually there, but if you turn it on, it breaks the manager), but we’ve run into some issues.

              Our Ant build scripts compress and minify the JS, and then concat them; but we’ve hit some issues with the *order* that the JS is being included in the file. For the events to properly proceed with the right object instances initialized, we’ve got to nail down the order that they’re being included.

              Obviously, that took low priority in getting beta-1 out. That development work is scheduled for either right before RC-1, or before RC-2. Once we get it working, however, you’ll be able to toggle compression on or off in the manager itself.
                shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                • 12512
                • 42 Posts
                hwmaier Reply #47, 17 years, 4 months ago
                Quote from: splittingred at Jun 09, 2009, 12:14 AM

                Quote from: hwmaier at Jun 09, 2009, 12:01 AM

                Is there anything else I should look at and report?
                Your specs look fine. The only other thing I can think of is to check and see if there’s any wayward errors in modx/core/cache/error.log that might be related, or if there’s any JS errors in the browser.

                No relevant entries in core/cache/logs/error.log.

                Below is an extract from Apache’s access.log and shows the requests made when mouseclicking on a node in the manager’s document tree. It’s not much data which gets requested but you can see it takes about 3 seconds. Strange.
                127.0.0.1 - - [09/Jun/2009:15:28:28 +1000] "GET /revolution/manager/index.php?a=40&id=1 HTTP/1.1" 200 23937
127.0.0.1 - - [09/Jun/2009:15:28:29 +1000] "GET /revolution/connectors/lang.js.php?topic=topmenu,file,resource,resource&action=40 HTTP/1.1" 200 31481
127.0.0.1 - - [09/Jun/2009:15:28:29 +1000] "GET /revolution/connectors/layout/modx.config.js.php?action=40 HTTP/1.1" 200 7101
127.0.0.1 - - [09/Jun/2009:15:28:29 +1000] "POST /revolution/connectors/resource/index.php HTTP/1.1" 200 1265
127.0.0.1 - - [09/Jun/2009:15:28:29 +1000] "POST /revolution/connectors/layout/tree/resource.php HTTP/1.1" 200 1586
127.0.0.1 - - [09/Jun/2009:15:28:30 +1000] "POST /revolution/connectors/layout/tree/element.php?action=getNodes&id=root HTTP/1.1" 200 2358
127.0.0.1 - - [09/Jun/2009:15:28:30 +1000] "POST /revolution/connectors/browser/directory.php?action=getList&id=root HTTP/1.1" 200 4518
127.0.0.1 - - [09/Jun/2009:15:28:30 +1000] "POST /revolution/connectors/layout/tree/resource.php?action=getNodes&id=root HTTP/1.1" 200 3139
127.0.0.1 - - [09/Jun/2009:15:28:30 +1000] "POST /revolution/connectors/layout/tree/resource.php?action=getNodes&id=web_0&type=context HTTP/1.1" 200 7195
127.0.0.1 - - [09/Jun/2009:15:28:31 +1000] "POST /revolution/connectors/layout/tree/resource.php?action=getNodes&id=web_1&type=modResource HTTP/1.1" 200 4791


                I will take a short video later too and publish it, so the visual effect is shown too.
                  • 12512
                  • 42 Posts
                  hwmaier Reply #48, 17 years, 4 months ago
                  Quote from: hwmaier at Jun 09, 2009, 12:42 AM

                  I will take a short video later too and publish it, so the visual effect is shown too.
                  Here is a link to a brief video clip showing the "slow" redraw of the document tree panel:
                  http://www.flickr.com/photos/31550227@N06/3609999793/
                    • 28215
                    • 4,149 Posts
                    splittingred Reply #49, 17 years, 4 months ago
                    Wait, you said 3-4 seconds. I counted maybe 1 second, 2 at worst.  rolleyes

                    Still vastly faster than any other system that makes you reload the page.
                      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                      • 16183
                      • 1,390 Posts
                      kongondo Reply #50, 17 years, 4 months ago
                      It is faster than what am experiencing on FF wink

                      /k
                        Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder