-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Optimize the optimizer #14477
Comments
Half a year later, we're still having an 'optimizer' 'optimizing' things for 10 mins.
Hooray!! |
I am upgrading kibana across our UAT and production stacks, and just the unpack of the kibana zip takes absolutely ages because of the file count. Please reduce! |
Over 1 year later nothing has changed |
Closing, no longer relevant as the optimizer will no longer be shipped after the legacy platform removal is complete. |
Extracting this on Windows is brutal. The optimizer is the reason for so many files? What is the optimizer? When will it be removed? |
Using node.js and a hefty number of node modules is the real reason for so many files. I'm working on removing the optimizer in #73154 and we're constantly trying to find ways to improve accountability and awareness of how many files are created in That said, I've heard that 7zip provides much better extraction performance on windows than the standard windows archive extraction tools, something to keep in mind if you're regularly extracting Kibana distributables. |
To dramatically decrease the file count and improve startup performance we should bundle the optimizer into a single is file.
The text was updated successfully, but these errors were encountered: