# Inconsistent data transfer performance from ES -\> Client **URL:** \ **Category:** Elasticsearch\ **Created:** [March 20, 2018, 7:44am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699 "2018-03-20T07:44:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![EvilCachew](https://avatars.discourse-cdn.com/v4/letter/e/a87d85/32.png) [@EvilCachew](https://discuss.elastic.co/u/EvilCachew)\ **Post date:** [March 20, 2018, 7:44am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699/1 "2018-03-20T07:44:52Z")
Hello We are very happy with our internal search performance within ES it self. However, transferring the data from ES to our client seems to perform rather inconsistent. I would be very happy to hear your suggestions as to how we can make this perform more consistent, or how I can better troubleshoot as to where by bottleneck appears. Information: - Every search is executed in 14-20ms based on the 'took' data from ES. - Very limited amount of data is transferred from ES to Client - Requests are made with GET/CURL timed using the 'time' command on a centos box Inconsistent data transfers timings: - Request 1: real 0m0.149s \*\*\* Request 2: real 0m0.027s\*\* - Request 3: real 0m0.150s - Request 4: real 0m0.148s \*\*\* Request 5: real 0m0.026s\*\* - Request 6: real 0m0.150s \*\*\* Request 7: real 0m0.026s\*\* \*\*\* Request 8: real 0m0.026s\*\* - Request 9: real 0m0.152s Any ideas / suggestions? 🙂 ---
**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:** [March 20, 2018, 7:56am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699/2 "2018-03-20T07:56:47Z")
Is your elasticsearch on the same LAN? ---
**Author:** ![EvilCachew](https://avatars.discourse-cdn.com/v4/letter/e/a87d85/32.png) [@EvilCachew](https://discuss.elastic.co/u/EvilCachew)\ **Post date:** [March 20, 2018, 8:01am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699/3 "2018-03-20T08:01:19Z")
No do not believe it is. It is a hosted environment run by ObjectRocket (ES) / Rackspace (CentOS). ---
**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:** [March 20, 2018, 8:16am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699/4 "2018-03-20T08:16:13Z")
So a network latency issue? ---
**Author:** ![EvilCachew](https://avatars.discourse-cdn.com/v4/letter/e/a87d85/32.png) [@EvilCachew](https://discuss.elastic.co/u/EvilCachew)\ **Post date:** [March 20, 2018, 8:26am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699/5 "2018-03-20T08:26:39Z")
Good suggestion, but it does not appear to be the actual issue we seeing. However, I think it led me on the right path 🙂 🙂 Added some additional timing data to my curl request based on your latency suggestion: [https://blog.josephscott.org/2011/10/14/timing-details-with-curl/](https://blog.josephscott.org/2011/10/14/timing-details-with-curl/) It seems like our issue may be with our DNS / namelookup: time\_namelookup: 0.125 ---
**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:** [March 20, 2018, 9:41am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699/6 "2018-03-20T09:41:07Z")
Great you found it... BTW did you look at the official [cloud.elastic.co](http://cloud.elastic.co) offer? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 17, 2018, 9:41am UTC](https://discuss.elastic.co/t/inconsistent-data-transfer-performance-from-es-client/124699/7 "2018-04-17T09:41:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.