We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28309
    • 12 Posts
    As I am Planning to built an application for client company with a current customer base of 500 following scenario:
    At any given time at least 450+ logged-in user will be participating in the various web service provided by the company.
    The number of Request will very from 450 to 8 times the logged in user.

    Zend framework1.6 handles 53 request per sec
    prado handles 60-80 request per sec
    yii handles 400 request per sec
    symphony handles 50-90 request per sec.

    (*above data is collected from some web resources)

    huh what about Modx?

    Please give me answer in urgent as i find modx much better as it requires less learning overhead,reusable component and maximum output in minimum time compared to others.
      • 22303 MODX Staff
      • 10,725 Posts
      Those are frameworks as well; saying that they can handle that many requests per second means what exactly? That if you write any code on the framework that it could potentially run that fast on some mythical super computer? I don’t understand where people are getting these numbers (other than out of thin air), or why they would ever be used for comparison. It’s like saying a car will go 500 mph with nothing but the chasis and wheels sitting on a machine; but it’s not going to be that way once you add all the useful stuff like seats, roofs, windows, people...
        • 25663 MODX Staff
        • 12,272 Posts
        We’ve deployed sites that handle millions of page views a day, of course that was over balanced servers and using a CDN on the back end. So conservatively, let’s just call it 1,000,000 page views with each page having 25 requests for the various images, CSS files, JS, etc. (in reality both numbers were higher).

        25,000,000 / 24 hours per day / 60 minutes per hour / 60 seconds per minute = 289 requests per second.

        Therefore, modx handles almost 300 requests per second. (put that on a shared server though and your figures would look insanely different tongue)
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 7231
          • 4,205 Posts
          25,000,000 / 24 hours per day / 60 minutes per hour / 60 seconds per minute = 289 requests per second.
          Sweet! I think that hardware will have a greater influence on negative performance than modx will.
            [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

            Something is happening here, but you don't know what it is.
            Do you, Mr. Jones? - [bob dylan]
            • 25663 MODX Staff
            • 12,272 Posts
            Please keep in mind that was a ridiculous example and could have scaled honestly to thousands of requests / sec just to illustrate your and Jason’s point: it’s all server dependent. Which of those frameworks listed can do everything modx can out of the box with no coding? Heck just limit that question to built in user and document permissions system and exclude the page tree, RTEs and file management bits.
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 28309
              • 12 Posts
              I am highly thankful to all of you for your quick response.

              As said by Ryan : Modx can handle nearly 300 request per sec.

              I feel glad to Inform I have decided to Use and Suggest Modx
              to my clients as base framework for their high traffic website.