Diploma Thesis Santiago GÃ³mez SÃ¡ez - IAAS

More documents

Recommendations

Info

7. Validation and Evaluation in the local MySQL database system. The response is received as a single statement which contains n result sets, one for each query in the multi-query. 7.3. Evaluation Extensions implemented in ServiceMix-mt may affect on its performance, and system’s resources consumption. Therefore, in this section we focus on evaluating, in the first place, the operative system’s resources the ESB consumes. In the second place, we evaluate the difference between connecting directly to the backend Cloud or local data store (without transparency to the user), and the utilization of a transparent connection through the Cloud- Enabled Data Access Bus. For evaluation purposes we utilize the TPC-H benchmark for generating the data, and Apache JMeter for performing the load tests. 7.3.1. TPC-H Benchmark The TPC-H benchmark is a set of libraries written in the C language which provide support for generating large volumes of data for populating the database system which wants to be evaluated [Tra01]. Furthermore, it generates queries with a high degree of complexity to be executed on the databases where the generated data is stored. In this diploma thesis we utilize the TPC-H benchmark to generate the data which is stored in the local MySQL database system, and in the backend MySQL database instances hosted in Amazon RDS. The data generated by the benchmark varies in size, and is stored in a database which follow the schema described in Figure 7.1. The TPC-H data and queries generator operations are mainly managed in two executables, which are generated by building the library with the make command: dbgen, and qgen. The former has as input option the size, which we set in this diploma thesis to 1GB, while the latter generates a set of queries for the generated data. After the data and queries generation, the user must manually import the data into the database system to evaluate. For more information about the processes of generating data and queries we attach in the prototype a short tutorial which is adjusted to the operative system we use in the FlexiScale’s VM: Ubuntu 10.04. 80
7.3. Evaluation Figure 7.1.: TPC-H database schema generated [Tra01]. 7.3.2. Evaluation Overview The system we set up for the evaluation is built up of three subsystems which are hosted in different infrastructures. The first subsystem resides in a private network provided in the University of Stuttgart, and identified by the hostname dyn139.iaas.uni-stuttgart.de. A local machine with Apache JMeter 2.9 installed is connected to the network. In the evaluation we aim to approach as much as possible to the motivating scenario: database layer migrated to the Cloud, and accessing the remote database system from the on-premise application’s data access layer. Therefore, we decide to perform the queries in a load generator program from a private network (see Figure 7.2). We classify in Figure 7.2 as the second subsystem the Amazon RDS database systems which are host in the Amazon Cloud [Amac]. Amazon provides the user with the option to deploy his database instances in different regions. We select the N. Virginia region, create the tenant 2 database on a db.m2.xlarge database instance, and transfer the table schemas and data generated by the TPC-H benchmark. For billing purposes we utilize the EDUStudentGrantsSpring- Summer2012 [Amaf] 81
Page 1:
Institute of Architecture of Applic
Page 5 and 6:
Contents 1. Introduction 1 1.1. Pro
Page 7 and 8:
Contents 7.3.3. Evaluation Analysis
Page 9 and 10:
List of Figures 1.1. Migration Scen
Page 11 and 12:
List of Tables 4.1. Description of
Page 13:
List of Listings 5.1. Tenant-aware
Page 16 and 17:
1. Introduction and multi-protocol
Page 18 and 19:
1. Introduction Definitions List of
Page 20 and 21:
1. Introduction • Implementation,
Page 22 and 23:
2. Fundamentals usage of it. PaaS p
Page 24 and 25:
2. Fundamentals 2.2.1. Enterprise S
Page 26 and 27:
2. Fundamentals through the network
Page 28 and 29:
Management Framework Component Fram
Page 30 and 31:
2. Fundamentals corresponding works
Page 32 and 33:
2. Fundamentals the tenant level, b
Page 34 and 35:
2. Fundamentals 2.9. Structured Que
Page 36 and 37:
2. Fundamentals 2.9.2. PostgreSQL D
Page 38 and 39:
2. Fundamentals 2.10.1. Key-value D
Page 40 and 41:
2. Fundamentals User Interface Web
Page 42 and 43:
28 2. Fundamentals
Page 44 and 45: 3. Related Works and balancing the
Page 46 and 47: 3. Related Works store may contain
Page 48 and 49: 3. Related Works In the second plac
Page 50 and 51: 4. Concept and Specification VM0 or
Page 52 and 53: 4. Concept and Specification then f
Page 54 and 55: 4. Concept and Specification 4.3. D
Page 56 and 57: 4. Concept and Specification 4.6. U
Page 58 and 59: 4. Concept and Specification Name G
Page 60 and 61: 4. Concept and Specification Name G
Page 62 and 63: 4. Concept and Specification 4.8.3.
Page 64 and 65: 5. Design stores have two main stor
Page 66 and 67: 5. Design userId serviceName XMLNam
Page 68 and 69: 5. Design received in the vendor’
Page 70 and 71: 5. Design JBI SA into an OSGi conta
Page 72 and 73: 5. Design Apache Camel provides a s
Page 74 and 75: 5. Design External Application Lege
Page 76 and 77: 5. Design External Application Exte
Page 78 and 79: 6. Implementation the bundle activa
Page 80 and 81: 6. Implementation each of the queri
Page 82 and 83: 6. Implementation multi-tenancy awa
Page 84 and 85: 6. Implementation The HTTP endpoint
Page 86 and 87: 6. Implementation stored. Both auth
Page 88 and 89: 74 6. Implementation
Page 90 and 91: 7. Validation and Evaluation We mus
Page 92 and 93: 7. Validation and Evaluation When t
Page 96 and 97: 1. Introduction 1. Introduction 7.
Page 98 and 99: 7. Validation and Evaluation proble
Page 100 and 101: 7. Validation and Evaluation access
Page 102 and 103: 8. Outcome and Future Work The func
Page 104 and 105: 90 8. Outcome and Future Work
Page 106 and 107: Appendix A. Components A.2. CDASMix
Page 108 and 109: 94 Appendix A. Components
Page 110 and 111: Appendix B. Messages 20 - target da
Page 112 and 113: Appendix B. Messages 110 111 - OK r
Page 114 and 115: Appendix B. Messages 1 interface: l
Page 116 and 117: 102 Appendix B. Messages
Page 118 and 119: Bibliography [CC06] F. Chong and G.
Page 120 and 121: Bibliography [SAS + 12] [SBK + 12]
Page 122 and 123: Acknowledgement I am heartily thank
show all

Diploma Thesis Santiago GÃ³mez SÃ¡ez - IAAS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?