[HBASE-20601] Add multiPut support and other miscellaneous to PE

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 3.0.0-alpha-1, 2.1.0
• Component/s: tooling

Release Note

1. Add multiPut support
Set --multiPut=number to enable batchput(meanwhile, --autoflush need be set to false)

2. Add Connection Count support
Added a new parameter connCount to PE. set --connCount=2 means all threads will share 2 connections.
oneCon option and connCount option shouldn't be set at the same time.

3. Add avg RT and avg TPS/QPS statstic for all threads

4. Delete some redundant code
Now RandomWriteTest is inherited from SequentialWrite.

• Assignee: Allan Yang
• Reporter: Allan Yang
• Created: 18/May/18 12:16
• Updated: 06/May/20 19:18
• Resolved: 24/May/18 02:04

Description

Add some useful stuff and some refinement to PE tool
1. Add multiPut support
Though we have BufferedMutator, sometimes we need to benchmark batch put in a certain number.
Set --multiPut=number to enable batchput(meanwhile, --autoflush need be set to false)

2. Add Connection Number support
Before, there is only on parameter to control the connection used by threads. oneCon=true means all threads use one connection, false means each thread has it own connection.
When thread number is high and oneCon=false, we noticed high context switch frequency in the machine which PE run on, disturbing the benchmark results(each connection has its own netty worker threads, 2*CPU IIRC).
So, added a new parameter connCount to PE. set --connCount=2 means all threads will share 2 connections.

3. Add avg RT and avg TPS/QPS statstic for all threads
Useful when we want to meansure the total throughtput of the cluster

4. Delete some redundant code
Now RandomWriteTest is inherited from SequentialWrite.

Issue Links

• is related to: HBASE-24340 PerformanceEvaluation options should not mandate any specific order