CQ Performance
Optimization Methodology
CQ Optimization Methodology

 5 Simple Rules that need to be followed for successful Performance
  Optimization


 Perfo...
Rule #1: Plan

Project Plan
                     Launch
               Soft Launch



                 1                  ...
Rule #2: Iterative Process



   Analyze                   Optimize



   Measure
                         Goal reached?
Rule #3: Goal




       Never optimize without
       a realistic goal.
       *taken from existing user behavior (access...
Rule #4: Get Real


       Load tests need to be
       “real”.
       Production size Content
       Production Code
    ...
Rule #5: Relevance




       Only optimize one
       bottleneck at a time.
       *don’t optimize things that “may be” m...
Suspects & Friends

 Check for the 2 usual suspects
   Dispatcher Cache Efficiency
   Search in “display scripts”


 F...
Upcoming SlideShare
Loading in …5
×

Day Communique Performance Optimization Methodology

3,307 views

Published on

A quick and simple guide for succesful performance optimization in general and specifically with Day Communique.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,307
On SlideShare
0
From Embeds
0
Number of Embeds
307
Actions
Shares
0
Downloads
42
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Day Communique Performance Optimization Methodology

  1. 1. CQ Performance Optimization Methodology
  2. 2. 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)
  3. 3. Rule #1: Plan Project Plan Launch Soft Launch 1 2 6-12 months First Optimization (allocate ~10% of overall development effort)
  4. 4. Rule #2: Iterative Process Analyze Optimize Measure Goal reached?
  5. 5. Rule #3: Goal Never optimize without a realistic goal. *taken from existing user behavior (access.log)
  6. 6. 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)
  7. 7. Rule #5: Relevance Only optimize one bottleneck at a time. *don’t optimize things that “may be” more efficient.
  8. 8. 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, ...)

×