Kibana: Optimize the optimizer

[spalger]

To dramatically decrease the file count and improve startup performance we should bundle the optimizer into a single is file.

[mkozjak]

Half a year later, we're still having an 'optimizer' 'optimizing' things for 10 mins.

{“type”:“log”,“@timestamp”:“2018-04-09T07:48:16Z”,“tags”:
[“info”,“optimize”],“pid”:9017,“message”:“Optimization of bundles for stateSessionStorageRedirect, 
status_page, timelion, sentinl, uauth and kibana complete in 600.08 seconds”}

Hooray!!

[matskmpbs]

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!

[schlangz]

Over 1 year later nothing has changed

[pgayvallet]

Closing, no longer relevant as the optimizer will no longer be shipped after the legacy platform removal is complete.

[realChevChelios]

Extracting this on Windows is brutal. The optimizer is the reason for so many files? What is the optimizer? When will it be removed?

[spalger]

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 https://github.com/elastic/kibana/pull/73154 and we're constantly trying to find ways to improve accountability and awareness of how many files are created in node_modules as the project grows, but still working on concrete ways to improve that.

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.