Apache9 commented on pull request #1858: URL: https://github.com/apache/hbase/pull/1858#issuecomment-640232998
Set up a 5 nodes cluster with the latest branch-2.2 code. Run `./bin/hbase pe --nomapred --presplit=5 randomWrite 10` To generated test data. Run `./bin/hbase pe --nomapred randomRead 10` Several times to load all data into block cache Run `./bin/hbase pe --rows=100000 --nomapred randomRead 10` Several times, before patch and after patch. Set --rows to 100k is because 1m rows requires too much time to finish. The latest result is Before patch: ``` 2020-06-07 22:54:30,362 INFO [main] hbase.PerformanceEvaluation: [RandomReadTest] Summary of timings (ms): [141302, 141522, 140684, 138496, 140165, 141211, 141792, 141077, 141257, 137735] 2020-06-07 22:54:30,418 INFO [main] hbase.PerformanceEvaluation: [RandomReadTest duration ] Min: 137735ms Max: 141792ms Avg: 140524ms 2020-06-07 22:54:30,418 INFO [main] hbase.PerformanceEvaluation: [ Avg latency (us)] 1403 2020-06-07 22:54:30,418 INFO [main] hbase.PerformanceEvaluation: [ Avg TPS/QPS] 7117 row per second ``` After patch: ``` 2020-06-07 22:49:25,923 INFO [main] hbase.PerformanceEvaluation: [RandomReadTest] Summary of timings (ms): [140656, 140635, 139256, 140225, 141125, 140199, 140405, 142181, 140379, 140557] 2020-06-07 22:49:25,980 INFO [main] hbase.PerformanceEvaluation: [RandomReadTest duration ] Min: 139256ms Max: 142181ms Avg: 140561ms 2020-06-07 22:49:25,980 INFO [main] hbase.PerformanceEvaluation: [ Avg latency (us)] 1403 2020-06-07 22:49:25,980 INFO [main] hbase.PerformanceEvaluation: [ Avg TPS/QPS] 7114 row per second ``` The avg latencies are between 139x-141x for both. As the difference before and after the patch is even smaller than the difference between each run, I do not think there is observable performance impact for the patch. Thanks. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
