# \[Stress Test\] JavaAPI Search Cost too much time with small index **URL:** \ **Category:** Elasticsearch\ **Created:** [October 18, 2012, 2:29pm UTC](https://discuss.elastic.co/t/stress-test-javaapi-search-cost-too-much-time-with-small-index/9408 "2012-10-18T14:29:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![zkidkid](https://avatars.discourse-cdn.com/v4/letter/z/fbc32d/32.png) [@zkidkid](https://discuss.elastic.co/u/zkidkid)\ **Post date:** [October 18, 2012, 2:29pm UTC](https://discuss.elastic.co/t/stress-test-javaapi-search-cost-too-much-time-with-small-index/9408/1 "2012-10-18T14:29:38Z")
Hi, Currently I am load test my search server, Bellow is detail: 1. I have 3 server running ES, each of them have 30Gb Ram & 24 Core. I set 20Gb for ES. 2. I have 3 webserver (Jetty) to receive request from client, then search in ES using java api, and then return json value. 3. I have a index which have small data, (about 50000 record, 345.7mb) To load test, I make a request to jetty server. (eg: /RandomSearch) In this doGet function, I just random one character value from a-z to search and then return value to client. My problem is, it's running too low: Here is stats: Start Current Num Indexed Total Time(ms) Rate (ms) Num Request(s) Num Searched Total Time(ms) Rate (ms) Num Request(s) 18.10.12 20:59:48 538 18.10.12 21:20:27 227 0 0 0.0 0 959626 526643575 548.801 826 But when I using head plugin ( myserver:9200/\_plugin/head/) to search, I notice that the result is really fast (eg: Searched 5 of 5 shards. 7588 hits. 0.046 seconds) I wonder whether I am wrong at java api request or java api is slower than http request ? The other problem is the json result is really slow. It take about 6-10 (second) to return to client. How could I improve that ? Thanks & Best Regards All. -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 18, 2012, 5:41pm UTC](https://discuss.elastic.co/t/stress-test-javaapi-search-cost-too-much-time-with-small-index/9408/2 "2012-10-18T17:41:53Z")
Can you share your load test scripts/programs ? Could be a nice way for other users to test their hardware or settings. David. De : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] De la part de kidkid Envoyé : jeudi 18 octobre 2012 16:30 À : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) Objet : [Stress Test] JavaAPI Search Cost too much time with small index. Hi, Currently I am load test my search server, Bellow is detail: 1. I have 3 server running ES, each of them have 30Gb Ram & 24 Core. I set 20Gb for ES. 2. I have 3 webserver (Jetty) to receive request from client, then search in ES using java api, and then return json value. 3. I have a index which have small data, (about 50000 record, 345.7mb) To load test, I make a request to jetty server. (eg: /RandomSearch) In this doGet function, I just random one character value from a-z to search and then return value to client. My problem is, it's running too low: Here is stats: Start Current Num Indexed Total Time(ms) Rate (ms) Num Request(s) Num Searched Total Time(ms) Rate (ms) Num Request(s) 18.10.12 20:59:48 538 18.10.12 21:20:27 227 0 0 0.0 0 959626 526643575 548.801 826 But when I using head plugin ( myserver:9200/\_plugin/head/) to search, I notice that the result is really fast (eg: Searched 5 of 5 shards. 7588 hits. 0.046 seconds) I wonder whether I am wrong at java api request or java api is slower than http request ? The other problem is the json result is really slow. It take about 6-10 (second) to return to client. How could I improve that ? Thanks & Best Regards All. -- -- ---
**Author:** ![zkidkid](https://avatars.discourse-cdn.com/v4/letter/z/fbc32d/32.png) [@zkidkid](https://discuss.elastic.co/u/zkidkid)\ **Post date:** [October 19, 2012, 9:21am UTC](https://discuss.elastic.co/t/stress-test-javaapi-search-cost-too-much-time-with-small-index/9408/3 "2012-10-19T09:21:51Z")
Hi, Current, we have a site with is running with lot of user. Then we make a script on this site so that every user will call to search for testing. In case you don't have a similar site, you could use Apache JMeter or CometD to load test your site. Currently, I'm looking a way to bring all data to memory. I still research LRU of ES to improve searching performance. Wait for your help all. Thanks. On Friday, October 19, 2012 12:41:59 AM UTC+7, David Pilato wrote: > Can you share your load test scripts/programs ? Could be a nice way for > other users to test their hardware or settings. > > David. > > _De :_ [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) \ [mailto: > [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) \] _De la part de_ kidkid > _Envoyé :_ jeudi 18 octobre 2012 16:30 > _À :_ [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) \ > _Objet :_ [Stress Test] JavaAPI Search Cost too much time with small > index. > > Hi, > > Currently I am load test my search server, Bellow is detail: > > 1. I have 3 server running ES, each of them have 30Gb Ram & 24 Core. I set > 20Gb for ES. > > 2. I have 3 webserver (Jetty) to receive request from client, then search > in ES using java api, and then return json value. > > 3. I have a index which have small data, (about 50000 record, 345.7mb) > > To load test, I make a request to jetty server. (eg: /RandomSearch) > > In this doGet function, I just random one character value from a-z to > search and then return value to client. > > My problem is, it's running too low: > > Here is stats: > > Start > > Current > > Num Indexed > > Total Time(ms) > > Rate (ms) > > Num Request(s) > > Num Searched > > Total Time(ms) > > Rate (ms) > > Num Request(s) > > 18.10.12 20:59:48 538 > > 18.10.12 21:20:27 227 > > 0 > > 0 > > 0.0 > > 0 > > 959626 > > 526643575 > > 548.801 > > 826 > > But when I using head plugin ( myserver:9200/\_plugin/head/) to search, I > notice that the result is really fast > > (eg: Searched 5 of 5 shards. 7588 hits. 0.046 seconds) > > I wonder whether I am wrong at java api request or java api is slower than > http request ? > > The other problem is the json result is really slow. It take about 6-10 > (second) to return to client. How could I improve that ? > > Thanks & Best Regards All. > > -- -- ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 20, 2012, 11:04pm UTC](https://discuss.elastic.co/t/stress-test-javaapi-search-cost-too-much-time-with-small-index/9408/4 "2012-10-20T23:04:30Z")
I would guess that the problem is somewhere in your app, then in elasticsearch. Its easy to test, use the total time returned from a search result and see if the problem is in the search executed by elasticsearch, or somewhere "above" it. On Oct 19, 2012, at 11:21 AM, kidkid [zkidkid@gmail.com](mailto:zkidkid@gmail.com) wrote: > Hi, > > Current, we have a site with is running with lot of user. > Then we make a script on this site so that every user will call to search for testing. > > In case you don't have a similar site, you could use Apache JMeter or CometD to load test your site. > > Currently, I'm looking a way to bring all data to memory. I still research LRU of ES to improve searching performance. > Wait for your help all. > > Thanks. > > On Friday, October 19, 2012 12:41:59 AM UTC+7, David Pilato wrote: > Can you share your load test scripts/programs ? Could be a nice way for other users to test their hardware or settings. > > David. > > De : [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) [[mailto:elasti...@googlegroups.com](mailto:elasti...@googlegroups.com)] De la part de kidkid > Envoyé : jeudi 18 octobre 2012 16:30 > À : [elasti...@googlegroups.com](mailto:elasti...@googlegroups.com) > Objet : [Stress Test] JavaAPI Search Cost too much time with small index. > > Hi, > > Currently I am load test my search server, Bellow is detail: > > 1. I have 3 server running ES, each of them have 30Gb Ram & 24 Core. I set 20Gb for ES. > > 2. I have 3 webserver (Jetty) to receive request from client, then search in ES using java api, and then return json value. > > 3. I have a index which have small data, (about 50000 record, 345.7mb) > > To load test, I make a request to jetty server. (eg: /RandomSearch) > > In this doGet function, I just random one character value from a-z to search and then return value to client. > > My problem is, it's running too low: > > Here is stats: > > Start > Current > Num Indexed > Total Time(ms) > Rate (ms) > Num Request(s) > Num Searched > Total Time(ms) > Rate (ms) > Num Request(s) > 18.10.12 20:59:48 538 > 18.10.12 21:20:27 227 > 0 > 0 > 0.0 > 0 > 959626 > 526643575 > 548.801 > 826 > > But when I using head plugin ( myserver:9200/\_plugin/head/) to search, I notice that the result is really fast > > (eg: Searched 5 of 5 shards. 7588 hits. 0.046 seconds) > > I wonder whether I am wrong at java api request or java api is slower than http request ? > > The other problem is the json result is really slow. It take about 6-10 (second) to return to client. How could I improve that ? > > Thanks & Best Regards All. > > -- > > -- -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:07am UTC](https://discuss.elastic.co/t/stress-test-javaapi-search-cost-too-much-time-with-small-index/9408/5 "2017-07-06T03:07:47Z")