Great result. When I changed thread count to *8* as per your suggestion,
'long running' warning messages disappeared. Thank you so much for your
promt support.
--
View this message in context:
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:
I executed in my windows machine. So the property file is
benchmark-win.properties.
Here I removed all benchmarks other than IgniteSqlQueryBenchmark.
set CONFIGS=^
-cfg %SCRIPT_DIR%\..\config\ignite-localhost-config.xml -b 1 -w 60 -d 300 -t
64 --server -sm PRIMARY_SYNC -dn IgniteSqlQueryBenchmark
Basically I execute only IgniteSqlQueryBenchmark from yardstick-ignite
project.
Following cache configuration used by this execution.
Hi All,
I am getting query too slow warning message while running Yardstick-ignite
benchmark. Not sure why indexed query is slow here.
machine configurations is 4 core CPU with 16 GB ram.
Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
WARNING: Query execution is too