Yes I got same kind of message from ThroughputLatencyProbe.csv file. --Probe dump file for probe: org.yardstickframework.probes.ThroughputLatencyProbe@12941d84 (class org.yardstickframework.probes.ThroughputLatencyProbe) --Created Tue Mar 28 12:00:45 IST 2017 --Benchmark config: BenchmarkConfiguration [memberId='-1', driverNames='[IgniteSqlQueryBenchmark]', serverName='IgniteNode', threads=64, duration=300, warmup=60, dfltProbeClsNames=[ThroughputLatencyProbe, PercentileProbe], propsFileName='..\config\benchmark-win.properties', packages=[org.yardstickframework, org.apache.ignite.yardstick], cmdArgs=[--outputFolder, results-3-01-115824, -cfg, D:\dev\workspace\yardstick-ignite-master\bin\..\config\ignite-localhost-config.xml, -b, 1, -w, 60, -d, 300, -t, 64, --server, -sm, PRIMARY_SYNC, -dn, IgniteSqlQueryBenchmark, -sn, IgniteNode, -ds, sql-query-1-backup, --config, ..\config\benchmark-win.properties], probeWriter='null', customProps={=: Note that each benchmark is set to run for 300 seconds (5 mins) with warm-up set to 60 seconds (1 minute)., BENCHMARK_PACKAGES=org.yardstickframework,org.apache.ignite.yardstick, -cfg=%SCRIPT_DIR%..configignite-localhost-config.xml -b 1 -w 60 -d 300 -t 64 --server -sm PRIMARY_SYNC -dn IgniteSqlQueryBenchmark -sn IgniteNode -ds sql-query-1-backup^, set=CONFIGS=^}, shutdownHook=true, currentFolder=null, scriptsFolder=null, logsFolder=null, outputFolder=results-3-01-115824, outputWriter=java.io.PrintStream@777817c0, errorWriter=java.io.PrintStream@6d5f7b86, descriptions=[sql-query-1-backup], hostName=] --Description: sql-query-1-backup
Also I did same way as you did to execute script. For you information, my machine is windows 7 with i5 4 core machine 3.20Ghz and 16 GB RAM. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Query-execution-is-too-long-warning-while-running-Yardstick-ignite-tp11348p11484.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.