Your SlideShare is downloading. ×
0
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Ignite Zurich   Newsweek
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Ignite Zurich Newsweek

2,855

Published on

Presentation by Meshach Jackson given at Ignite Zurich conference by Day Software. - 09/2009

Presentation by Meshach Jackson given at Ignite Zurich conference by Day Software. - 09/2009

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,855
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
42
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. CMS Smackdown Selecting Newsweekʼs Future
    • 2. Our Mission ➡ The First Place for the Last Word ➡ First Wave ➡ Deeply Connected ➡ Highly Organic
    • 3. Current Landscape ➡ Unpredictable Traffic ➡ Horrible Editorial Workflow ➡ Inflexible Development Environment
    • 4. Case Studies
    • 5. Case Studies
    • 6. Case Studies
    • 7. Case Studies
    • 8. Why CQ5? ➡ Rapid Application Development ➡ Seamless 3rd Party Integration ➡ Cloud-Friendly Architecture
    • 9. Why CQ5? ➡ Cloud-Friendly Architecture Price Performance
    • 10. Why CQ5? Price Amazon Cloud > $15k / mo + > $5k setup Data Center < $20k / mo + $300k setup
    • 11. Why CQ5? Performance Quiz App vs. Geometrixx
    • 12. Why CQ5? Performance Quiz App vs. Geometrixx ➡ Ruby on Rails ➡ HAProxy LB ➡ 1 MySQL db ➡ AWS “Small” Instances
    • 13. Why CQ5? Performance Quiz App vs. Geometrixx ➡ Ruby on Rails ➡ HAProxy LB ➡ 1 MySQL db ➡ AWS “Small” Instances ...x 29
    • 14. Why CQ5? Performance Quiz App vs. Geometrixx ➡ CQ5 ➡ Ruby on Rails ➡ AWS ELB ➡ HAProxy LB ➡ “Medium” Instances - ➡ 1 MySQL db Dispatcher ➡ AWS “Small” Instances ➡ “XL” Instances - CQ5/ ...x 29 CRX
    • 15. Why CQ5? Performance Quiz App vs. Geometrixx ➡ CQ5 ➡ Ruby on Rails ➡ AWS ELB ➡ HAProxy LB ➡ “Medium” Instances - x 4 ➡ 1 MySQL db Dispatcher ➡ AWS “Small” Instances ➡ “XL” Instances - CQ5/ x 2 ...x 29 CRX
    • 16. Why CQ5? Performance Quiz App vs. Geometrixx ➡ CQ5 ➡ Ruby on Rails ➡ AWS ELB ➡ HAProxy LB ➡ “Medium” Instances - x 4 ➡ 1 MySQL db Dispatcher ➡ AWS “Small” Instances ➡ “XL” Instances - CQ5/ x 2 ...x 29 CRX
    • 17. Load Test - RESULTS Quiz App vs. Geometrixx Test 1: Goal - 10k users in 1 hr Duration - 20 min
    • 18. Load Test - RESULTS Quiz App vs. Geometrixx Test 1: Goal - 10k users in 1 hr Duration - 20 min Result: 2,500 users 31k errors 5.6 sec response times
    • 19. Load Test - RESULTS Quiz App vs. Geometrixx Test 1: Goal - 10k users in 1 hr Duration - 20 min Result: 2,500 users 31k errors 5.6 sec response times FAIL
    • 20. Load Test - RESULTS Quiz App vs. Geometrixx Test 2: Goal - 100 users in 5 min Duration - 30 min Result: 100 users 138 errors 1.1 sec response time
    • 21. Load Test - RESULTS Quiz App vs. Geometrixx Test 2: Goal - 100 users in 5 min Duration - 30 min Result: 100 users 138 errors 1.1 sec response time FAIL
    • 22. Load Test - RESULTS Quiz App vs. Geometrixx Test 3: Result: 2,500 users 51 errors 331 ms response time
    • 23. Load Test - RESULTS Quiz App vs. Geometrixx Test 3: Result: 2,500 users 51 errors 331 ms response time eh...
    • 24. Load Test - RESULTS Quiz App vs. Geometrixx Test 1: (w/ ELB) Goal - 5k users in 15 min Duration - 6 min Result: ELB Failure
    • 25. Load Test - RESULTS Quiz App vs. Geometrixx Test 2: (w/o ELB) Goal - 2.5k users in 15 min Duration - 18 min Result: 2,500 users < 20 ms response time 288k HTTP requests / min 3MM total HTTP requests
    • 26. Load Test - RESULTS Quiz App vs. Geometrixx Test 2: (w/o ELB) Goal - 2.5k users in 15 min Duration - 18 min Result: 2,500 users < 20 ms response time 288k HTTP requests / min 3MM total HTTP requests 0 errors
    • 27. Load Test - RESULTS Quiz App vs. Geometrixx Test 3: (w/o ELB) Goal - break it. (10k users in 15 min) Duration - 17 min Result: 3,333 users 350k HTTP requests / min 10k users = 1 sec response time 498 ms avg response time 5MM total HTTP requests
    • 28. Whatʼs Next? On-Publish Semantic Processing On-Publish Social Distribution Organic Social Evolution Editorial Workflow Authoring Single Sign On Authentication Premium Content Provider Citizen Journalism Awesome Web Apps Semantic Comment Processing

    ×