-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Reduce security
& spaces
plugin bundle sizes
#64192
Labels
performance
Team:Security
Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
v7.8.0
Comments
mshustov
added
performance
Team:Security
Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
v7.8.0
labels
Apr 22, 2020
Pinging @elastic/kibana-security (Team:Security) |
17 tasks
ACK: taking a look at the Security plugin management sections first, as they have a bigger impact. |
I believe we've made reasonable improvements during last couple of weeks and we can close this issue for now. We'll try to track bundle sizes on a constant basis until we get automation for that. Here is what we have in master now:
|
lizozom
changed the title
Reduce Security & Spaces plugins bundle size
Reduce Apr 18, 2022
security
& spaces
plugin bundle sizes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
performance
Team:Security
Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
v7.8.0
The current bundle sizes:
security.plugin.js - 2.7Mb
spaces.plugin.js - 1.8Mb
We can reduce the size by adding lazy loading for management section components.
kibana/src/plugins/management/public/types.ts
Line 59 in 8e17fda
Kibana loading performance in one of the critical problems to address in the current release. Let me know if you manage to squeeze the issue in the remaining time until FF. Otherwise, I can help to implement it.
Useful links https://github.com/elastic/kibana/blob/master/src/core/MIGRATION.md#how-to-understand-how-big-the-bundle-size-of-my-plugin-is
The text was updated successfully, but these errors were encountered: