# Benchmarking results investigation **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [May 25, 2018, 11:18am UTC](https://discuss.elastic.co/t/benchmarking-results-investigation/133309 "2018-05-25T11:18:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![AdamBoi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adamboi/32/31508_2.png) [@AdamBoi](https://discuss.elastic.co/u/AdamBoi)\ **Post date:** [May 25, 2018, 11:18am UTC](https://discuss.elastic.co/t/benchmarking-results-investigation/133309/1 "2018-05-25T11:18:38Z")
Hello. I'd like to discuss an issue. I've got some results after running custom track on elasticsearch index. [Custom track used for benchmarking](https://github.com/AdamDubnytskyy/custom_track/blob/master/track.json) | Lap | Metric | Task | Value | Unit | | --- | --- | --- | --- | --- | | All | Indexing time | | 0.0715 | min | | All | Indexing throttle time | | 0 | min | | All | Merge time | | 0.0864333 | min | | All | Refresh time | | 0.132483 | min | | All | Flush time | | 0.00181667 | min | | All | Merge throttle time | | 0 | min | | All | Total Young Gen GC | | 0.062 | s | | All | Total Old Gen GC | | 0 | s | | All | Store size | | 0.976847 | GB | | All | Translog size | | 0.0157164 | GB | | All | Heap used for segments | | 2.97031 | MB | | All | Heap used for doc values | | 0.553997 | MB | | All | Heap used for terms | | 2.17584 | MB | | All | Heap used for norms | | 0.0727539 | MB | | All | Heap used for points | | 0.0613871 | MB | | All | Heap used for stored fields | | 0.106339 | MB | | All | Segment count | | 109 | | | All | 50th percentile latency | test generic request time | 2.09754 | ms | | All | 90th percentile latency | test generic request time | 3.99158 | ms | | All | 99th percentile latency | test generic request time | 8.00824 | ms | | All | 99.9th percentile latency | test generic request time | 26.267 | ms | | All | 100th percentile latency | test generic request time | 43.0159 | ms | | All | 50th percentile service time | test generic request time | 1.96887 | ms | | All | 90th percentile service time | test generic request time | 3.84714 | ms | | All | 99th percentile service time | test generic request time | 6.25481 | ms | | All | 99.9th percentile service time | test generic request time | 10.8736 | ms | | All | 100th percentile service time | test generic request time | 12.8791 | ms | | All | **error rate** | test generic request time | **100** | % | 2018-05-24 12:15:49,565 PID:9160 rally.reporting WARNING No throughput metrics available for [test generic request time]. Likely cause: Error rate is 100.0%. Please check the logs. 2018-05-24 12:15:49,566 PID:9160 rally.metrics INFO Closing metrics store. 2018-05-24 12:15:49,567 PID:9152 rally.racecontrol INFO Benchmark has finished successfully. 2018-05-24 12:15:49,567 PID:9152 rally.racecontrol INFO Telling benchmark actor to exit. 2018-05-24 12:15:49,568 PID:9160 rally.racecontrol INFO BenchmarkActor received unknown message [ActorExitRequest] (ignoring). However as you can see I've got 100% of error rate. Looking into the logs there is next point that could be connected with error rate metric beeing 100%. Every single query results with a HTTP 400 Bad Request Response **2018-05-24 12:15:48,917 PID:9222 elasticsearch WARNING GET [http://172.19.0.3:9200/index\_name\_20180516105114/\_search?request\_cache=false](http://172.19.0.3:9200/index_name_20180516105114/_search?request_cache=false) [status:400 request:0.001s]** On the other hand running same query via curl from my local machine responds with a traditional 200 response and a document returned by elasticsearch. Do you have any thoughts about possible issue? Thank you. ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [May 25, 2018, 11:57am UTC](https://discuss.elastic.co/t/benchmarking-results-investigation/133309/2 "2018-05-25T11:57:11Z")
Hi, I had a look at your track and you specify `_source` inside `query` but this should be specified on top-level instead. So the correct query body is: ```auto { "_source": [ "property_type_id", "park_code", "platform_options.bvdir", "property_type_id", "parameters", "location", "rating", "stars", "number_of_survays", "labels", "park_code", "coordinates", "id", "availabilities_with_min_prices", "availabilities_with_max_prices" ], "from": 0, "size": 10, "sort": [ { "_score": "desc" }, { "sorting.global_points_2": "desc" } ], "query": { "bool": { "filter": [ { "term": { "platform": "bvdir" } }, { "term": { "demo": false } } ] } } } ``` You can also try to run Rally with `--on-error="abort"` and see more error details. Daniel ---
**Author:** ![AdamBoi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adamboi/32/31508_2.png) [@AdamBoi](https://discuss.elastic.co/u/AdamBoi)\ **Post date:** [May 25, 2018, 12:19pm UTC](https://discuss.elastic.co/t/benchmarking-results-investigation/133309/3 "2018-05-25T12:19:00Z")
Thank you Daniel. Finally it works for me. And thats great. I'm happy! Have inspiration to delve into _esrally docs_ to experiment more widely with the tool. Cheers! ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [May 25, 2018, 1:16pm UTC](https://discuss.elastic.co/t/benchmarking-results-investigation/133309/4 "2018-05-25T13:16:03Z")
Hi Adam, glad to hear that it's resolved now. 🙂 Daniel ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 22, 2018, 1:16pm UTC](https://discuss.elastic.co/t/benchmarking-results-investigation/133309/5 "2018-06-22T13:16:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.