We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19388
    • 297 Posts
    There is something to see the page render time? Snippet? Plugin? Log? Placeholder?
      • 22303 MODX Staff
      • 10,725 Posts
      Quote from: mIDO at May 23, 2011, 08:31 AM

      There is something to see the page render time? Snippet? Plugin? Log? Placeholder?
      Basically the same as it was in Evolution, though the database queries and database time are not accurate in Revolution due to some technical issues.

      e.g.
      <div>
      <p>Total time — [^t^]</p>
      <p>Resource from — [^s^]</p>
      </div>
        • 19388
        • 297 Posts
        Thank you. I thought it was not going to work because the tag syntax. I’ve seen something interesting and is the fact that a simple [[If]] snippet execution takes a lot of time!.

        I’ve reduced the page load time in two seconds just caching three calls to this snippet. This is normal? :S
          • 19388
          • 297 Posts
          Caching tree if snippet calls and two getResources I went from 3,2seconds page load time to 0,3 laugh
          What I don’t understand is the If snippet performance ...
            • 22303 MODX Staff
            • 10,725 Posts
            If your use of the IF snippet can be cached, great, it will only add to the time when the Resource cache items are rebuilt.

            FWIW, after editing in Revo 2.0.x, the ALL of the cache files, including the Context cache, has to be regenerated before the page can be parsed and rendered. This is why you are seeing the very large load times on first access. It’s not just the Resource being processed. In 2.1.x, the Context cache file is generated by the process of saving or "refreshing" rather than "clearing" the cache, so page load times after editing will appear much faster in 2.1.
              • 19388
              • 297 Posts
              For this reason I made some tests not only one. My use of if can be cached fortunately, but I think performance of this snippet can be revised. But I suposse that is not the snippet itself, but the internal process of executing a snippet in MODX.
              This website is using 2.0.7 in a Windows Machine