Introduction to CCS & Examples of Run Time Performance

Items
What is CCS? Why Cloud? Benefits

What is CCS?
CUBE Cloud Services A cloud based environment for travel demand modeling in CUBE

Why Cloud?
Speed Scalability Sharing Ease of access Easy to manage

Speed
Inherent utilization of Cube Cluster Model Administrators choose how many cores make sense for their models Choose from 1 to 1001 cores Runtimes charged in core-hours.

Scalability
Any number of Users Any number of Scenarios All running simultaneously One preconfigured machine image
No model distribution, setup, or support Guaranteed consistent results Only pay for what you use

Sharing
Publish your model Publish your standard datasets Invite Users.
Choose access level (applier group). Choose to sponsor users (or not). No model distribution, setup, or support. Guaranteed Consistent Results. Monitor usage and activity.

Easy Access
Highly available Web-based Interface
Access from anywhere Access anytime Access on any device

Simple data uploads and downloads Email notifications

User Invites Scenario Completion

Benefits
Community Resource: model application and planning analysis done by nonexperts using common web-browsers moving models to an active role in collaborative transportation planning Cloud-Computing: placement of the models, data and software in a cloudcomputing environment lowering hardware costs locally while providing unlimited high-spec resources Lower costs for the user: movement from locally licensed desktops to a software as a service model. Monthly subscription business model allowing many to use the model at low, or even, no cost Lessens IT complexity: much of the IT burden of modeling is shifted from the user to the vendor

Nashville
Activity Based Model 2,174 zones 1,257,000 person records 6,000,000 activity records generated 4 Time-Of-Day assignments (AM,MD,PM,OP) 2 user-classes

Nashville (Minimum # of Cores =8 )

Run Times (Hours) 200 192 184 176 168 160 152 144 136 128 120 112 104 96 88 80 72 64 56 48 40 32 24 16 8 0

175.2

139.1

Hours

53.7

25 12.7 10

99% reduction off single core

7.3 512

16

32

64 Number of Cores

128

256

Charlotte
Time-Of-Day highway assignment model 3,000 zones 4 time periods 3 pathloads in each assignment

Charlotte
Run Times (Hours) 120 114

100

80

Minutes

60

40 30 24 20 18 12

90% reduction off single core

0 1 8 16 Number of Cores 32 64

VTA
2,980 zones 7 peak period highway assignments 6 user classes Feedback loop

VTA
Run Times (Hours) 24 22 20 18 16 14 Hours 12 10 8 6 4 2 0 1 8 16 Number of Cores 32 64 7.7 5.8 4.9 21.4

80% reduction off single core

4.3

FLSWM
Statewide model 6,242 zones Passenger and freight modeling 4 user classes

FLSWM
Run Times (Hours) 12 11.4

10

Hours

3.3 2.3

72% reduction off single core

2.1

0 1 8 Number of Cores 16 32