search

pravega / pravega-benchmark

Performance benchmark tool for Pravega
Apache License 2.0
8 stars 22 forks source link

Issue 94: Log test parameters at start of run #96

Closed maddisondavid closed 4 years ago

maddisondavid commented 4 years ago

Change log description Logs the parameters being used by the test before it starts

Purpose of the change Fixes #94

What the code does Before the test starts the parameters being used by the test are logged, i.e. 

>./pravega-benchmark -controller tcp://localhost:9090 -consumers 1 -scope dave -stream dave5  -segments 5 -time 5
2020-01-17 10:24:41:836 +0000 [main] INFO io.pravega.perf.PravegaPerfTest - Test Parameters: streamName='dave5', rdGrpName='dave5RdGrp', scopeName='dave', recreate=false, writeAndRead=false, producerCount=0, consumerCount=1, segmentCount=5, segmentScaleKBps=0, segmentScaleEventsPerSecond=0, scaleFactor=2, events=0, eventsPerSec=0, eventsPerProducer=0, eventsPerConsumer=0, EventsPerFlush=2147483647, transactionPerCommit=0, runtimeSec=5, throughput=-1.0, writeFile='null', readFile='null', startTime=1579256681824, enableConnectionPooling=true, writeWatermarkPeriodMillis=-1, readWatermarkPeriodMillis=-1
2020-01-17 10:24:42:106 +0000 [main] INFO io.pravega.client.stream.impl.ControllerImpl - Controller client connecting to server at localhost:9090
2020-01-17 10:24:42:109 +0000 [main] INFO io.pravega.client.stream.impl.ControllerImpl - Controller client connecting to server at localhost:9090
2020-01-17 10:24:42:116 +0000 [main] WARN io.pravega.client.netty.impl.ConnectionPoolImpl - Epoll not available. Falling back on NIO.

The change is very simple and I opted for using the toString() in order to quickly retrieve the parameters. This means in future it should also be easy to keep it up to date when new parameters are added.

Signed-off-by: David Maddison david.maddison@dell.com