Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve kibana loading process #7433

Closed
zhihuiFan opened this issue Jun 12, 2016 · 2 comments
Closed

improve kibana loading process #7433

zhihuiFan opened this issue Jun 12, 2016 · 2 comments

Comments

@zhihuiFan
Copy link

kibana is so cool so that I want to put all the data into elasticsearch and then visualize them with kibana.
But to integrate with our existing tool, I need to ember their dashboard to our existing page. Thanks to the "share" function in kibana 4, I can do this easily.

However the issue I run into the is kibana performance. In an overview, it takes ~10 seconds to load a simple dashboard and after a bit of deep, I found most of the time is used to dowload commons.bundle.js and kibana.bundle.js.

do we have a way to improve this? like compress the js file or something similar? is there any suggested action I can take now for this issue?

thanks

@zhihuiFan
Copy link
Author

screen shot 2016-06-12 at 2 47 38 pm

this is a snapshot which shows where the time is cost.

@Bargs
Copy link
Contributor

Bargs commented Jun 13, 2016

In the future, please ask operational questions like this in our discussion forums: https://discuss.elastic.co/c/kibana. We try to reserve Github for bugs and feature requests.

We do have an existing enhancement request for setting proper cache control headers on these static files, which should help your problem. #6520

Until that's fixed, however, the best you might be able to do is set the headers yourself with a proxy in front of Kibana.

@Bargs Bargs closed this as completed Jun 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants