CQ Performance
Optimization Methodology

CQ Optimization Methodology
 5 Simple Rules that need to be followed for successful Performance
Optimization
 Performance optimization is a matter of experience.
 Expectations of system performance are very important in the Performance
Optimization Process.
 CQ Best Practices: 100ms / uncached html request max (check here)
 Up the capacity (scaling)
 Lower the burden (optimization)

Rule #1: Plan
Project Plan
Launch
Soft Launch
1 2
6-12 months
First Optimization
(allocate ~10% of overall
development effort)

Rule #2: Iterative Process
Analyze Optimize
Measure
Goal reached?

Rule #3: Goal
Never optimize without
a realistic goal.
*taken from existing user behavior (access.log)

Rule #4: Get Real
Load tests need to be
“real”.
Production size Content
Production Code
Production Infrastructure Setup
Production number of Users
Production Load (as close as reasonable)

Rule #5: Relevance
Only optimize one
bottleneck at a time.
*don’t optimize things that “may be” more efficient.

Suspects & Friends
 Check for the 2 usual suspects
 Dispatcher Cache Efficiency
 Search in “display scripts”
 False usual suspects
 JVM Tuning
 OS Tuning
 Check in with your best friends
 request.log
 component timing in html comments
 Java Profiler (yourkit, ...)