# Memory allocation for query/kibana servers

**URL:** https://discuss.elastic.co/t/memory-allocation-for-query-kibana-servers/60952
**Category:** Elasticsearch
**Created:** [September 19, 2016, 10:37pm UTC](https://discuss.elastic.co/t/memory-allocation-for-query-kibana-servers/60952 "2016-09-19T22:37:21Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![stecino](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@stecino](https://discuss.elastic.co/u/stecino)
#### Post date: [September 19, 2016, 10:37pm UTC](https://discuss.elastic.co/t/memory-allocation-for-query-kibana-servers/60952/1 "2016-09-19T22:37:21Z")

</div>

Hello,

I have 795GB index (5shards, 1replica), 783million documents. Each record has about 35 fields. When I do query of the whole thing through kibana I get query results back in about 90seconds. My query/kibana node has 16GB memory allocated for elasitcsearch. I was wondering, other than trying to reduce my index size, I wanted to understand how index size on disk is translated into query result size in memory in query node and passed onto kibana. What kind of hardware adjustments, scaling, caching I could implement to get faster query response.

I am in the process if building a cluster with ES 2.3.4 and kibana 4.5 and logstash 2.4

Thanks in advance

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:18pm UTC](https://discuss.elastic.co/t/memory-allocation-for-query-kibana-servers/60952/2 "2017-07-05T22:18:59Z")

</div>