Ignite Zurich   Newsweek
Upcoming SlideShare
Loading in...5
×
 

Ignite Zurich Newsweek

on

  • 3,141 views

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

Statistics

Views

Total Views
3,141
Views on SlideShare
3,134
Embed Views
7

Actions

Likes
3
Downloads
40
Comments
0

4 Embeds 7

http://www.slideshare.net 4
http://www.linkedin.com 1
http://www.slideee.com 1
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Ignite Zurich   Newsweek Ignite Zurich Newsweek Presentation Transcript

  • CMS Smackdown Selecting Newsweekʼs Future
  • Our Mission ➡ The First Place for the Last Word ➡ First Wave ➡ Deeply Connected ➡ Highly Organic
  • Current Landscape ➡ Unpredictable Traffic ➡ Horrible Editorial Workflow ➡ Inflexible Development Environment
  • Case Studies
  • Case Studies
  • Case Studies
  • Case Studies
  • Why CQ5? ➡ Rapid Application Development ➡ Seamless 3rd Party Integration ➡ Cloud-Friendly Architecture
  • Why CQ5? ➡ Cloud-Friendly Architecture Price Performance
  • Why CQ5? Price Amazon Cloud > $15k / mo + > $5k setup Data Center < $20k / mo + $300k setup
  • Why CQ5? Performance Quiz App vs. Geometrixx
  • Why CQ5? Performance Quiz App vs. Geometrixx ➡ Ruby on Rails ➡ HAProxy LB ➡ 1 MySQL db ➡ AWS “Small” Instances
  • Why CQ5? Performance Quiz App vs. Geometrixx ➡ Ruby on Rails ➡ HAProxy LB ➡ 1 MySQL db ➡ AWS “Small” Instances ...x 29
  • 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
  • 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
  • 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
  • Load Test - RESULTS Quiz App vs. Geometrixx Test 1: Goal - 10k users in 1 hr Duration - 20 min
  • 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
  • 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
  • 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
  • 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
  • Load Test - RESULTS Quiz App vs. Geometrixx Test 3: Result: 2,500 users 51 errors 331 ms response time
  • Load Test - RESULTS Quiz App vs. Geometrixx Test 3: Result: 2,500 users 51 errors 331 ms response time eh...
  • Load Test - RESULTS Quiz App vs. Geometrixx Test 1: (w/ ELB) Goal - 5k users in 15 min Duration - 6 min Result: ELB Failure
  • 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
  • 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
  • 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
  • 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