Day Communique Performance Optimization Methodology
CQ Optimization Methodology
5 Simple Rules that need to be followed for successful Performance
Performance optimization is a matter of experience.
Expectations of system performance are very important in the Performance
CQ Best Practices: 100ms / uncached html request max (check here)
Up the capacity (scaling)
Lower the burden (optimization)
Rule #1: Plan
(allocate ~10% of overall
Rule #2: Iterative Process
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
Production size Content
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
Check in with your best friends
component timing in html comments
Java Profiler (yourkit, ...)