1. BY VAIBHAV NACHANKAR ARVIND DWARAKANATH Evaluation of Hbase Read/Write (A study of Hbase and it’s benchmarks)

2. Recap of Hbase Hbase is an open-source, distributed, column- oriented and sorted-map data storage. It is a Hadoop Database; sits on HDFS. Hbase can support reliable storage and efficient access of a huge amount of structured data

3. Hbase Architecture

4. Recap of Hbase (contd.) Modeled after BigTable. Map/reduce with Hadoop. Optimizations for real time queries. No single point of failure. Random access performance is like MySQL. Application : Facebook Messaging Database.

5. Hbase Benchmark Techniques ‘Hadoop Hbase-0.20.2 Performance Evaluation’ by D. Carstoiu, A. Cernian, A. Olteanu. University of Bucharest. STRATEGY: Uses random read, writes to test and benchmark Hadoop with Hbase.

6. Hbase Benchmark Techniques (contd.) ‘Hadoop Hbase-0.20.2 Performance Evaluation’ by Kareem Dana at Duke University. It shows a varied set of test cases for executions to test HBase. STRATEGY: Tested on column families, columns, Sort and interspersed read/writes.

7. Yahoo! Cloud Serving Benchmark (YCSB) ‘Benchmarking Cloud Serving Systems with YCSB’ by Brian F. Cooper, Adam Silberstein, Erwin Tam, Raghu Ramakrishnan, Russell Sears. This paper/project is designed to benchmark existing and newer cloud storage technologies. The benchmark is done so far on Hbase, Cassandra, MongoDb, Project Voldemort and SQL.

8. YCSB The benchmark tool uses Workload files and the workload files can be customized according to users. You can specify 50/50 read/write, 95/5 r/w and so on. The code for the project is available on Github. https://github.com/brianfrankcooper/YCSB.git

9. Example of a Workload # Yahoo! Cloud System Benchmark # Workload A: Update heavy workload # Application example: Session store recording recent actions # # Read/update ratio: 50/50 # Default data size: 1 KB records (10 fields, 100 bytes each, plus key) # Request distribution: zipfian recordcount=1000 operationcount=1000 workload=com.yahoo.ycsb.workloads.CoreWorkload readallfields=true readproportion=0.5 updateproportion=0.5 scanproportion=0 insertproportion=0

10. Example of a Workload # Yahoo! Cloud System Benchmark # Workload B: Read mostly workload # Application example: photo tagging; add a tag is an update, but most operations are to read tags # # Read/update ratio: 95/5 # Default data size: 1 KB records (10 fields, 100 bytes each, plus key) # Request distribution: zipfian recordcount=1000 operationcount=1000 workload=com.yahoo.ycsb.workloads.CoreWorkload readallfields=true readproportion=0.95 updateproportion=0.05 scanproportion=0 insertproportion=0

11. Our Project Install Hbase and get Hadoop to interface with it. Study benchmark techniques. Build a suite of codes and get it to run on Hadoop/Hbase. Include basic get, put, scan operations. Extend Word Count’s map-reduce to add to Hbase. Compare with Brisk Cassandra.

12. About Brisk Cassandra is a No-SQL BigTable-based database. Datastax enterprise built Brisk to interface Hadoop with Cassandra Hadoop + Cassandra = Brisk!!

13. Brisk Architecture

14. Challenges Faced Configuration of Hbase is a tedious job! Not for the weak of will! Hbase subsequent releases do not keep the APIs consistent. So we ran into a lot of ‘deprecated API’ error messages. Hadoop compatibility with Hbase has to be verified before we proceed with installations.

15. Challenges Faced (contd.) Very few documents on installation details of Hbase. Even fewer for Brisk!

16. Performance for Word Count (2 nodes/2 cores each) Average = 45.484

17. Performance for Word Count (contd.)

18. Average = 43.7008

19. Performance for a simple get/put/scan (2 nodes/ 2 core)

20. Performance for Word Count (3 nodes/2 cores each) Number of Readings

21. Performance for Word Count (contd.) Average = 36.1012 Time in secs

22. Performance for Word Count (contd.) Average = 37.4358

23. Conclusions Brisk seems a lot more promising tool; as it integrates Cassandra and Hadoop together without much ado. Hbase/Hadoop APIs have to be made consistent. With standardization, it would be easier to work with them. Hbase Reads are faster than the Writes.

24. Thank You Questions??