Performance Testing: the front-end, the back-end, the whole damn fish!

Session Speaker(s): 
Saturday, November 8 2014
Room: Mushroom Kingdom
Time: 2:30pm - 3:30pm


What this session will cover:

The difference between concurrent users and user sessions

Learn how to identify and build individual usage scenarios

The metrics that will help in developing realistic workload characterizations

Learn how to identify and model special considerations (APIs, Forms, Personalization)

Learn how to construct realistic workload models

Writing a Performance Test Plan

  • When a heavy load is applied to the site, where do bottlenecks emerge?

  • What page response times can anonymous users expect?

  • What page response times can authenticated users expect?

  • How well does the Drupal caching layer protect APIs from heavy traffic?

Overall system availability and response time are the key metrics that will result from the tests performed.

Types of Tests

  • Consistent Load Test Scenarios

  • Stress Test Scenarios


·       Average Response time (in seconds)

·       Average hits per second

·       Total transactions per second (passed and failed)

·       Total errors

·       Slow queries identified

·       CPU, Memory utilization

·       Load Balancer, Varnish, Database analysis

·       Throughput

·       Possible bottlenecks identified

Test Environments and tools

Timeline for Performance Testing

Performance Goals

  • Acceptable page response times

  • Concurrency estimation

  • Current Editorial statistics

Reporting and Remediation


Optimizing the front-end