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

[Security Solution][Tech Debt] Improve the lazy loaded chunks for security_solution by resolving the duplication. #142773

Open
YulNaumenko opened this issue Oct 5, 2022 · 2 comments
Labels
8.6 candidate Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture

Comments

@YulNaumenko
Copy link
Contributor

YulNaumenko commented Oct 5, 2022

Current size of the lazy loaded chunks for security_solution is very impactful for the application performance, because we are loading most of the modules twice:

We have at least 4 chunks with the same code duplication, which contains all the security sub plugins in:

Screen Shot 2022-10-27 at 9 02 41 AM

Screen Shot 2022-10-27 at 9 02 57 AM

Screen Shot 2022-10-27 at 9 03 11 AM

@YulNaumenko YulNaumenko added technical debt Improvement of the software architecture and operational architecture Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. 8.6 candidate labels Oct 5, 2022
@YulNaumenko YulNaumenko self-assigned this Oct 5, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@stephmilovic
Copy link
Contributor

related: #143574

@YulNaumenko YulNaumenko removed their assignment Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.6 candidate Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Development

No branches or pull requests

3 participants