Vaadin scalability-slides

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”

DOM

Client Server

ViewHTML Page

over HttpResponse

Controller

Model

Parameters overHttpRequest

DB2

3

4

5

1


Client-side RIA

DOM

Client Server

View

Controller

Model

DB2

3

4

5

1

Requested datato view as

XML / JSON

Changes to modelencoded as parameters


Server-side RIA

DOM

Client Server

ViewHTML Pageover HttpResponse

Controller

Model

Parameters overHttpRequest

DB4

5

6

2

Term

inalAdapter

Term

inalAdapter

Automated bythe RIA framework

3

7

1

9

8

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


up to

1.9 billiontickets per month


up to

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

rvat

ions

paid

tick

ets


Business Logic

Memcached

MySQL DB

cities, ...

reservations

paidtickets

cities, ...


Vaadin

Logic

UI

Cache

MySQL DB

Tomcat

Vaadin

Logic

UI

Cache

Tomcat

Vaadin

Logic

UI

Cache

Tomcat


Tomcat Tomcat Tomcat

MySQL

ELB

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



RDS-Large• $0.44 / hour


Benchmark


Test Tomcat Tomcat

ELB

Apache JMetertestrecording


Test Tomcat Tomcat

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

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

ELB


Test Tomcat Tomcat

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

Apa

che

JMet

er

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


Scenarios per minute

One Tomcat Server

0

600

1200

1800

2400

3000

Sales / Minute0

30

60

90

120

150

Avg response (ms)

2000 3000 4000 5000 6000

Average ajax response (ms)

Concurrent simulated users usersperjantaina 21. tammikuuta 2011


One Tomcat Server

0

600

1200

1800

2400

3000

Sales / Minute0

30

60

90

120

150

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

0

1200

2400

3600

4800

6000

Sales / Minute0

80

160

240

320

400

Avg response (ms)

2000 3000 4000 5000 6000 18000



3 se

rver

s

3 se

rver

s

1 server 1 server


3 xservers

2.6 xtransactions


What if we overload the server?



Three Tomcat Servers

0

1200

2400

3600

4800

6000

Sales / Minute0

400

800

1200

1600

2000

Avg response (ms)

2000 3000 4000 5000 6000 18000 28000



3 se

rver

s

3 se

rver

s

1 server

2 se

rver

s

2 se

rver

s

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

[email protected]+358-40-5035001skype://joonaslehtinen


mailto:[email protected]
















Documents

Vaadin scalability-slides