Answers: <p>So basically I've ended up turning these flags off (<code>/app/management/kibana/settings</code>)</p>
  <pre><code>filterEditor:suggestValues
  discover:searchOnPageLoad
  doc_table:highlight
  visualize:enableLabs
  telemetry:enabled
  </code></pre>
  <p>Other ideas I had in mind:</p>
  <ul>
  <li>adding nginx as a proxy caching all the static files (js for plugins / images)</li>
  <li>warmup script (periodically makes requests to predefined hot pages for Kibana to internally cache these pages) if that would work</li>
  <li>migrate to hosted cloud solution which might be optimized better for the loading time</li>
  </ul>
  
Answers: CC BY-SA 4.0
Answers: 2020-11-04T13:14:57.463Z
Answers: 2020-11-04T13:14:57.463Z
Answers: Most Wanted
Body: <p>I have a Kibana page which takes about 7-10 seconds to load.</p>
  <p>Benchmarking same page shows ~1s to complete the request</p>
  <pre><code>$ ab -n 10 &quot;http://kibana/app/discover#/view/15a67850-6921-11ea-8308-058e42e28132&quot;
  </code></pre>
  <p>and the exact same query to elastic takes about 1s to complete as well.</p>
  <pre><code>$ ab -n 20 -p same-query.json -T application/json &quot;http://kibana:9200/logstash*/_search&quot;
  </code></pre>
  <p>It's just 2 simple <code>match</code> filters within a request to <code>logstash*</code> index.
  Taking into account benchmarking above I don't think the the issue related to Elasticsearch/Logstash but rather to Kibana itself. So my questions are:</p>
  <ol>
  <li>Is the a way to tune/optimize performance for Kibana (page loading time)?</li>
  <li>In case I move Kibana UI to separate instance will that give any benefits to performance? (currently it's ELK stack on the one instance 8 vcpus, 16 GiB memory)</li>
  <li>How can I additionally narrow down the exact reason of this slow performance?</li>
  </ol>
  
Comments: CC BY-SA 4.0
Comments: 2020-11-04T07:57:37.337Z
Comments: What ELK version do you use ?
Comments: pioupiou
Comments: CC BY-SA 4.0
Comments: 2020-11-04T09:43:44.400Z
Comments: ELK version is 7.9.2
Comments: Most Wanted
Tags: <azure><performance><ubuntu><elk><kibana>
Title: Kibana slow performance optimization
UserDisplayName: Most Wanted
ThreadText: # Kibana slow performance optimization
  
  (Asked by: username_0 on 2020-10-29)
  
  I have a Kibana page which takes about 7-10 seconds to load.
  
  Benchmarking same page shows ~1s to complete the request
  
  ```
  $ ab -n 10 "http://kibana/app/discover#/view/15a67850-6921-11ea-8308-058e42e28132"
  
  ```
  
  and the exact same query to elastic takes about 1s to complete as well.
  
  ```
  $ ab -n 20 -p same-query.json -T application/json "http://kibana:9200/logstash*/_search"
  
  ```
  
  It's just 2 simple `match` filters within a request to `logstash*` index.
  Taking into account benchmarking above I don't think the the issue related to Elasticsearch/Logstash but rather to Kibana itself. So my questions are:
  
  1. Is the a way to tune/optimize performance for Kibana (page loading time)?
  2. In case I move Kibana UI to separate instance will that give any benefits to performance? (currently it's ELK stack on the one instance 8 vcpus, 16 GiB memory)
  3. How can I additionally narrow down the exact reason of this slow performance?
  
  **Tags:** azure, performance, ubuntu, elk, kibana
  
  > **Comments:**
  > **username_1**: What ELK version do you use ?  
  > **username_0**: ELK version is 7.9.2  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-11-04. Score: 3 | Accepted answer
  
  So basically I've ended up turning these flags off (`/app/management/kibana/settings`)
  
  ```
  filterEditor:suggestValues
  discover:searchOnPageLoad
  doc_table:highlight
  visualize:enableLabs
  telemetry:enabled
  
  ```
  
  Other ideas I had in mind:
  
  * adding nginx as a proxy caching all the static files (js for plugins / images)
  * warmup script (periodically makes requests to predefined hot pages for Kibana to internally cache these pages) if that would work
  * migrate to hosted cloud solution which might be optimized better for the loading time
  
  
  ---
  
  