We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10449
    • 956 Posts
    That should be visible with a simple phpinfo()

    btw, insert this in a template (at the bottom) to view some modx-generated stats:

    <!--
    
    MySQL: [^qt^], [^q^] request(s), PHP: [^p^], total: [^t^], document retrieved from [^s^].
    
    -->

      • 9207 ☆ A M B ☆
      • 2,475 Posts
      Oh, THAT stuff... yeah... that would be an easy way to to look at it.

      phpinfo() is available in the manager, btw: Reports-->System Info

      I have a loaded module: mod_cgi
      and: GATEWAY_INTERFACE CGI/1.1

      I guess that means I’m not running fast-cgi, right?
        • 22303 MODX Staff
        • 10,725 Posts
        Quote from: Everett at May 08, 2009, 02:07 PM

        How does Zend’s Performance Suite compare to eAccelerator? The eAccelerator code hasn’t been updated in a while, so I’d tend to lean towards Zen.
        I currently have no experience with any opcode caches other than eAccelerator, sorry.

        Quote from: Everett at May 08, 2009, 03:58 PM

        I have a loaded module: mod_cgi
        and: GATEWAY_INTERFACE CGI/1.1

        I guess that means I’m not running fast-cgi, right?
        Correct. In fact, that’s probably your biggest problem. I would suggest running it as a server module (easiest and fastest performance) and looking at FastCGI only if the reasons are very compelling. Unfortunately, those debates are beyond my expertise at the moment...
          • 9207 ☆ A M B ☆
          • 2,475 Posts
          those debates are beyond my expertise at the moment...

          Yeah, mine too... I’ve never had the uh... pleasure (?)... of playing admin on a server that gets this kind of traffic, so the problems and solutions are unfamiliar.

          Slow query log... enabling fast-cgi... those are places to start.