We are currently using TransportClient and observing that query response times are considerably slower than using http (through sense plugin). Below is code snippet for initializing TransportClient: > void createClient(Map<String, String> props) { Settings settings = ImmutableSettings.settingsB…

What is "considerably slower"? What are the queries you execute? How do you measure query response time? It's not visible in the code.

The following query has been generated using SearchRequestBuilder.toString() API from the elastic search client library version 1.4.3 GET /index-1/_search { "from": 0, "size": 10, "query": { "filtered": { "query": { "multi_match": { "query": "2015 Chevrolet Cruze", …

Yes, QUERY_THEN_FETCH. We have also referred to link and have set explain to false.

I'm willing to dive deeper into this. Things would be easier to trace with query profiling https://github.com/elastic/elasticsearch/pull/6699 but it's not ready yet. The fact is that HTTP uses Java under the hood so HTTP can not be faster than Java. Maybe you can try to repeat the case with node …

Is there any additional parameter that gets passed by the Java client versus HTTP/Sense? The results given above are with 11 primaries and 1 replica. We repeated the tests with 7 primaries and 1 replica. But the results are the same. This is why we suspect that there is some additional parameter th…

Node client has a different cluster rendezvous. It sends discovery request (multicast or unicast ping), then joins the cluster and is visible to all nodes. Transport client tries to connect to TCP/IP host addresses and uses these hosts as a proxy to access the cluster nodes. It does not join the cl…

Thanks... Help me understand... When you say that "different times are measured"... I didn't quite get this. When I execute the query using Sense, I get back a JSON response and it has an attribute called took. Similarly when I execute the same query using elasticsearch client library I get back S…

Java Client slower than http

Elastic Stack Elasticsearch

jprante (Jörg Prante) June 11, 2015, 9:12pm 4

And search type https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-search-type.html is the same in both requests?

Topic		Replies	Views
Native Java API is slower than the REST one Elasticsearch	3	1521	July 5, 2017
Elasticsearch Transport client performance vs. Sense plugin Elasticsearch	7	1426	July 5, 2017
Elasticsearch Java client much slower than rest call Elasticsearch	7	4361	July 5, 2017
Performance Transport vs REST client Elasticsearch	4	1869	September 8, 2017
Java Transport Client slower than curl request Elasticsearch	10	2947	July 5, 2017

Java Client slower than http

Related topics