Database Reference
In-Depth Information
Cloudstone benchmark
L1
M/N satisfies predefined read/write ratio
M write
operations
L2
Master
Replication within the same region and the same availability zone
Slave 1
Slave k
Slave k+ 1
Slave n
Replication within the same region but across availability zones
L3
Slave 1
Slave k
Slave k+ 1
Slave n
Replication across regions
Slave 1
Slave n
Slave 1
Slave n
Slave 1
Slave n
Slave 1
Slave n
us-west
eu-west
ap-southeast
ap-northeast
FIGURE 11.3
Database replication on virtualized cloud servers.
early. Both the master database server and the application benchmark are deployed in
us - east -1 a location. The third layer is a group of slaves that are responsible for process-
ing read operations and updating write sets. The number of slaves in a group varies
from one to the number where throughput limitation is achieved. Several options for
the deployment locations of the slaves have been used, namely, the same zone as the
master in us - east -1 a , a different zone in us-east- 1 b , and four possible different regions,
ranging among us-west , eu - west , ap - southeast , and ap - northeast . All slaves run in
small instances for the same reason of provisioning the master instance.
Several sets of experiments have been implemented to investigate the end-to-end
throughput and the replication delay. Each of these sets is designed to target a spe-
cific configuration regarding the geographical locations of the slave databases and
the read/write ratio. Multiple runs are conducted by compounding different work-
loads and numbers of slaves. The benchmark is able to push the database system to a
limit where no more throughput can be obtained by increasing the workload and the
number of database replicas. Every run lasts 35 minutes, including 10-minute ramp-
up, 20-minute steady stage, and 5-minute ramp down. Moreover, for each run, both
the master and slaves should start with a preloaded, fully synchronized database.
11.5.3 e nD - to -e nD t hroughPut e XPeriments
Figures 11.4 and 11.5 show the throughput trends for up to 4 and 11 slaves with mixed
configurations of three locations and two read/write ratios. Both results indicate that
Search WWH ::




Custom Search