Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

gh-66 reorganize directory structure

  • Loading branch information...
commit 2e57c546cbdbe7a3542a0d41cf278738c1ebe9c1 1 parent 75af673
Michi Mutsuzaki authored
View
47 README
@@ -1,42 +1,29 @@
Yahoo! Cloud System Benchmark (YCSB)
+====================================
+Links
+-----
http://wiki.github.com/brianfrankcooper/YCSB/
http://research.yahoo.com/Web_Information_Management/YCSB
ycsb-users@yahoogroups.com
+Getting Started
+---------------
-Overview
-========
+1. Download the latest release of YCSB:
-It is difficult to decide which system is right for your application,
-partially because the features differ between systems, and partially
-because there is not an easy way to compare the performance of one
-system versus another.
+ wget https://github.com/downloads/brianfrankcooper/YCSB/ycsb-0.1.4.tar.gz
+ tar xfvz ycsb-0.1.4
+ cd ycsb-0.1.4
-The goal of the YCSB project is to develop a framework and common set
-of workloads for evaluating the performance of different "key-value"
-and "cloud" serving stores. The project comprises two things:
+2. Set up a database to benchmark. There is a README file under each binding
+ directory.
-* The YCSB Client, an extensible workload generator
+3. Run YCSB command.
-* The Core workloads, a set of workload scenarios to be executed by
- the generator
+ bin/ycsb load basic workloads/workloada
+ bin/ycsb run basic workloads/workloada
-Although the core workloads provide a well rounded picture of a
-system's performance, the Client is extensible so that you can define
-new and different workloads to examine system aspects, or application
-scenarios, not adequately covered by the core workload. Similarly, the
-Client is extensible to support benchmarking different
-databases. Although we include sample code for benchmarking HBase and
-Cassandra, it is straightforward to write a new interface layer to
-benchmark your favorite database.
-
-A common use of the tool is to benchmark multiple systems and compare
-them. For example, you can install multiple systems on the same
-hardward configuration, and run the same workloads against each
-system. Then you can plot the performance of each system (for example,
-as latency versus throughput curves) to see when one system does
-better than another.
-
-Detailed information about using the benchmark is available in the
-doc/index.html file.
+ Running the `ycsb` command without any argument will print the usage. See
+ https://github.com/brianfrankcooper/YCSB/wiki/Core-Properties for the list
+ of available workload properties.
View
0  distribution/src/main/bin/ycsb → bin/ycsb
File renamed without changes
View
0  distribution/src/main/bin/ycsb.sh → bin/ycsb.sh
File renamed without changes
View
43 distribution/src/main/assembly/distribution.xml
@@ -5,19 +5,42 @@
<format>tar.gz</format>
</formats>
<includeBaseDirectory>true</includeBaseDirectory>
+ <fileSets>
+ <fileSet>
+ <directory>..</directory>
+ <outputDirectory>.</outputDirectory>
+ <fileMode>0644</fileMode>
+ <includes>
+ <include>README</include>
+ <include>CHANGELOG</include>
+ <include>LICENSE.txt</include>
+ <include>NOTICE.txt</include>
+ </includes>
+ </fileSet>
+ <fileSet>
+ <directory>../bin</directory>
+ <outputDirectory>bin</outputDirectory>
+ <fileMode>0755</fileMode>
+ </fileSet>
+ <fileSet>
+ <directory>../workloads</directory>
+ <outputDirectory>workloads</outputDirectory>
+ <fileMode>0644</fileMode>
+ </fileSet>
+ </fileSets>
<moduleSets>
<moduleSet>
<useAllReactorProjects>true</useAllReactorProjects>
<includeSubModules>true</includeSubModules>
<sources>
- <includeModuleDirectory>false</includeModuleDirectory>
+ <includeModuleDirectory>true</includeModuleDirectory>
+
<fileSets>
<fileSet>
- <directory>../</directory>
- <outputDirectory>.</outputDirectory>
- <includes>
+ <directory>.</directory>
+ <fileMode>0644</fileMode>
+ <includes>
<include>README</include>
- <include>CHANGELOG</include>
</includes>
</fileSet>
<fileSet>
@@ -25,16 +48,6 @@
<outputDirectory>conf</outputDirectory>
<fileMode>0644</fileMode>
</fileSet>
- <fileSet>
- <directory>src/main/bin</directory>
- <outputDirectory>bin</outputDirectory>
- <fileMode>0755</fileMode>
- </fileSet>
- <fileSet>
- <directory>src/main/resources/workloads</directory>
- <outputDirectory>workloads</outputDirectory>
- <fileMode>0644</fileMode>
- </fileSet>
<fileSet>
<outputDirectory>lib</outputDirectory>
<directory>target</directory>
View
0  ...on/src/main/resources/workloads/workloada → workloads/workloada
File renamed without changes
View
0  ...on/src/main/resources/workloads/workloadb → workloads/workloadb
File renamed without changes
View
0  ...on/src/main/resources/workloads/workloadc → workloads/workloadc
File renamed without changes
View
0  ...on/src/main/resources/workloads/workloadd → workloads/workloadd
File renamed without changes
View
0  ...on/src/main/resources/workloads/workloade → workloads/workloade
File renamed without changes
View
0  ...on/src/main/resources/workloads/workloadf → workloads/workloadf
File renamed without changes
Please sign in to comment.
Something went wrong with that request. Please try again.