Performance Testing | Community
Skip to main content
Z
ZackTurnbow
October 16, 2015
Solved

Performance Testing

  • October 16, 2015
  • 4 replies
  • 1426 views

Referencing http://dev.day.com/docs/en/cq/5-4/managing/conceptandplanning.html#Setting%2520Target%2520Metrics

Under the section of Performance > Setting Response Times, it mentions guidelines for page response times under controlled circumstances. I would like to know how those numbers where determined. I also would like to know what test/testing software is used to validate those numbers. I'm trying to determine is the CQ system that I inherited is configured and optimized correctly.

Thank you for your time.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Gardner_Buchana

    Performance, load and scalability testing of web applications is a pretty large subject area these days.  One good place to see what people do and talk to others doing application performance testing is SQA Forums, a popular Software testing and quality verification discussions site.

    http://qaforums.com/

    The most popular tools, industry wide, are probably

    There are many other options.

    Within Adobe, we tend to use JMeter extensively for small projects and unit level testing, and a commercial load generation tools for public facing applications and larger more complex systems.  JMeter is very flexible for unit level automated tests as there is no licensing complexity, but JMeter's scenario capturing and editing is limited, as is its ability to do analysis and reporting of results.  Commercial tools we commonly use are HP LoadRunner as well as Borland SilkPerformer (http://www.borland.com/products/silkperformer/). Both of these have very powerful scenario editing, load modelling and analysis and reporting capabilities.

    4 replies

    Gardner_Buchana
    Gardner_Buchana
    Level 2
    October 16, 2015

    The document reference is to the 5.4 version.  This is the current version of that documentation:

    http://dev.day.com/docs/en/cq/current/managing/conceptandplanning.html

    In both versions, the section Setting target response times describes the process of deciding what your performance goals are and how you will measure whether your system meets them.  The actual numbers in this section are made up for the purposes of example.  The numbers represent requirements that might be applied to a typical web application, irrespective of the technology -- you might look for performance characteristics of this type from an IIS/ASP.NET application, for example.  They are not meant to describe the actual performance of any particular CQ/AEM application.

    If you are looking for guidance about the actual capacity or performance of a realistic CQ/AEM application, I would suggest looking at the following forum posting for links to that sort of information:

    http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__nhc7-some_of_theselinks.html

      smacdonald2008
      smacdonald2008
      Level 10
      October 16, 2015

      This question was passed on to the CQ performance team. 

      Z
      ZackTurnbowAuthor
      October 16, 2015

      Thank you for the quick reply. I have read most of those links already. I was hoping for a more explanation of how Adobe tests their own installations. I will find away that suits my needs.

      Gardner_Buchana
      Gardner_BuchanaAccepted solution
      Level 2
      October 16, 2015

      Performance, load and scalability testing of web applications is a pretty large subject area these days.  One good place to see what people do and talk to others doing application performance testing is SQA Forums, a popular Software testing and quality verification discussions site.

      http://qaforums.com/

      The most popular tools, industry wide, are probably

      There are many other options.

      Within Adobe, we tend to use JMeter extensively for small projects and unit level testing, and a commercial load generation tools for public facing applications and larger more complex systems.  JMeter is very flexible for unit level automated tests as there is no licensing complexity, but JMeter's scenario capturing and editing is limited, as is its ability to do analysis and reporting of results.  Commercial tools we commonly use are HP LoadRunner as well as Borland SilkPerformer (http://www.borland.com/products/silkperformer/). Both of these have very powerful scenario editing, load modelling and analysis and reporting capabilities.

        Terms & ConditionsAccessibility statement

        Loading footer...