R7507/3355a6f84543master
master vs async
Commit | Author | Details | Committed | ||||
---|---|---|---|---|---|---|---|
3f39cac8bec5 | dfquaresma/Sean Busbey | [elasticsearch5-rest] add forgotten elasticsearch5-rest binding. | Sep 13 2018 | ||||
b31a5681b9c6 | liukun/Sean Busbey | [basicdb] Modifty the example for basicdb in order to adapt to the curd… | Sep 3 2018 | ||||
f79a40e7dd55 | Robert S Lee/Sean Busbey | [jdbc] support JDBC option to rewrite batch statement to multi-row insert… | Aug 27 2018 | ||||
d1a8a6949c0a | allanbank/GitHub | Merge pull request #1217 from stutiredboy/master | Aug 20 2018 | ||||
47cb4079241f | Sean Busbey | [release] Update README for the release of YCSB 0.15.0 | Aug 17 2018 | ||||
668d5a87ee4e | ChenXiaosheng <tiredboy@> | form MongoDB 4.0: update mongodb-java-driver to 3.8 | Aug 16 2018 | ||||
8f57b1ac3863 | isuntsov/Sean Busbey | [ignite] fix Ignite README.md. (#1215) | Aug 13 2018 | ||||
51320479412f | Sean Busbey | [ignite, ignite-sql] update to Apache Ignite (incubating) version 2.6.0 | Jul 30 2018 | ||||
c506ef90b7f3 | Sean Busbey | [version] update master to 0.16.0-SNAPSHOT | Jul 29 2018 |
README
Yahoo! Cloud System Benchmark (YCSB)
http://wiki.github.com/brianfrankcooper/YCSB/ http://research.yahoo.com/Web_Information_Management/YCSB ycsb-users@yahoogroups.com
Overview
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.
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:
- The YCSB Client, an extensible workload generator
- The Core workloads, a set of workload scenarios to be executed by the generator
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.