We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3232
    • 380 Posts
    deleting it completely saves about a second of php time. we are making progress.

    It looks like i have some poor templates/snipplets and will have to revisit each.,

    To prove this i set up a clean install of modxcms and it has great render times.

    thank you all for your help and guidance. I will let you know how I make out and see if i can find the offending call.

    Furthermore it appears that there is a ditto call eating up the time ~1.3 sec which searched about 7 containers with filters
      • 22303 MODX Staff
      • 10,725 Posts
      Quote from: betoranaldi at Jun 03, 2007, 03:08 PM

      Futhermore it appears that there is a ditto call eating up the time ~1.3 sec which searched about 7 containers with filters
      Why not cache those calls? I’d never run Ditto uncached on a live site. Great for development, but Ditto should only actually execute after a change is made to your site, right?
        • 3232
        • 380 Posts
        Maybe I don’t understand cached calls correctly but don’t they only recache itself once that particular page is updated? so if a document is updated in another portion of the site, unless the page that has the snippet call is recached the new document won’t show up. Also i sometimes use snippets within a snippet call which requires the outermost call to use [! !] and the inner call to use [[ ]].

          • 3232
          • 380 Posts
          I don’t mean to bring up an old post but wanted to let everyone know what was causing the slowdown.

          It turns out when I transfered my snippets in assets/snippets/xxx -- I didn’t make all of the directories writable. Therefore, one snippet in general (GoogleEvents) couldn’t write a cache file which was causing 2 - 6 second php parse times. Once I made this folder writable the site sped-up considerably .3 sec php parse times.

          Thanks for everyone’s help

          -Brian