Vaadin scalability-slides

transcript

Joonas Lehtinen, PhDVaadin Ltd, CEO

Server-side RIA Scalability

perjantaina 21. tammikuuta 2011

Vaadin is a UI framework

for desktop-like web apps

htmljava

Vaadin valueproposition

simplerforget the web cost-effective

no JavaScript debuggingmodular

extensible ♲

powerfulall Java tools& libraries

more securecode stays in server

open sourcefree Apachelicense

BUTperjantaina 21. tammikuuta 2011

Does ItScale?

Server-side RIA?

“Web 1.0”

Client Server

ViewHTML Page

over HttpResponse

Controller

Parameters overHttpRequest

Client-side RIA

Client Server

Controller

Requested datato view as

XML / JSON

Changes to modelencoded as parameters

Server-side RIA

Client Server

ViewHTML Pageover HttpResponse

Controller

Parameters overHttpRequest

inalAdapter

Automated bythe RIA framework

Handled by the framework

Scale?

Server-side RIA Scalability questions

Initial application download and Ajax traffic

Server-side CPUusage by the user interface logic

Server-side memory consumption per session

Top 3 Questions

AnswerDepends on your application

Useful AnswerScales enough for most applications

Big enough application toprove the point?

Movie ticket reservationsystem

Think BIG

238 countries

6 624 theaters

69 347 rooms

20.7M seats

3 movies per night

1.9 billiontickets per month

224 billion! per year[ assuming 10! / ticket ]

which is 10X total global box office sales of 30 billion USD in 2009 estimated by MPAA

assume• 10% fill rate to reach global sales in 2009• 2 tickets per sales transaction

we should be able to handle2140 sales transactions per minute on average - 24/7(assuming uniform load)

How it’s made?

Vaadin Framework

Business Logic

User Interface Logic

MySQL DB

Business Logic

MySQL DB

countriescities

theatersshows

... rese

Business Logic

Memcached

MySQL DB

cities, ...

reservations

paidtickets

cities, ...

Vaadin

MySQL DB

Tomcat

Vaadin

Tomcat

Vaadin

Tomcat

Tomcat Tomcat Tomcat

EC2-Large• 7.5GB mem• 2 CPU cores• $0.34 / hour

RDS-Large• $0.44 / hour

Benchmark

Test Tomcat Tomcat

Apache JMetertestrecording

Test Tomcat Tomcat

t t t t 14 JMeter servers (EC2-Large)2000 threads per server

Test Tomcat Tomcat

t t t t 14 JMeter servers (EC2-Large)2000 threads per server

Scenarios per minute

One Tomcat Server

Sales / Minute0

Avg response (ms)

2000 3000 4000 5000 6000

Average ajax response (ms)

Concurrent simulated users usersperjantaina 21. tammikuuta 2011

One Tomcat Server

Sales / Minute0

Avg response (ms)

2000 3000 4000 5000 6000

Concurrent simulated users users

GOAL all tickets in 20092140

Goal of selling all tickets in the

world reached with only one

server!

What happens with multiple servers?

Three Tomcat Servers

Sales / Minute0

Avg response (ms)

2000 3000 4000 5000 6000 18000

1 server 1 server

3 xservers

2.6 xtransactions

What if we overload the server?

Three Tomcat Servers

Sales / Minute0

Avg response (ms)

2000 3000 4000 5000 6000 18000 28000

1 server

Too many users

5 x latency

98% of the transactions

per server

Optimizations

1. Profile memory

2. Explicit session clear in the end

3. Minimize database use

4. Move static resources to AWS CloudFront

Expected hostingcosts?

Servers

3 x Tomcat Server (EC2-Large)$2730 / year total (reserved instance)

1 x MySQL Server (RDS-Large)$910 / year (reserved instance)

Total $3640 / year

Network

Elastic Load Balancing$8819 / year

1050TB traffic$86000 / year

Total $94819 / year

Total hosting costs

Hosting costs are 0.00043% of the ticket sales revenues sales

$87 per million sales transactions

Total hosting costs: $100.000 / year

QuestionsComments

joonas@vaadin.com+358-40-5035001skype://joonaslehtinen

Vaadin scalability-slides

Documents