416DAT

Artifact Content
Login

Artifact 85d1ce16660e789fa838ab95cd54dace5842077e:

Wiki page [Milestone 2] by jfang 2013-03-21 06:57:06.
D 2013-03-21T06:57:06.169
L Milestone\s2
P d284c12ad42359d78ce85b6f56ced6e80c921440
U jfang
W 1588
<h1>Goals</h1>
<p>
Our goal for the next iteration is to run a variety of workloads on all databases, and generate graphs to compare each database under different workloads.
<br>We will run each workload with different number of threads, number of nodes, method of data distribution/replication.
<br>If time permits, we will test how well each database fare against failure such as node failure.
</p>
<h1>Current plan to complete the project (65% done)</h1>
<h2>Completed:</h2>
<ul>
<li>
Each group member has their assigned database (Redis, Cassandra, Couchbase, OrientDB, MongoDB) already installed on at least one of five Amazon instances. 
</li><br>
<li>
We have also installed YCSB on the instances and ran some initial tests to ensure that inserting, updating, and reading records works for a single instance.
</li>
</ul>
<h2>In Progress:</h2>
<ul>
<li>
We are currently working on setting up the distributed configuration for each of our databases. 
</li>
</ul>
<h2>To Do:</h2>
<ul>
<li>
As soon as the distributed setup is complete, we expect to start collecting performance data on a small amount of records (e.g. 10,000) and then scaling up incrementally due to limited storage space on the Amazon instances.
</li><br>
<li>
We will then analyze the collected data and compare the performance of each database and represent the differences visually using graphs.
</li><br>
<li>
Time permitting, we will also be investigating how each database behaves/performs in the event of node failure and include our findings in our final report.
</li>
</ul>
Z bb0b8c1a95b7294af2b4d5f3daf22e90