Optimizing and caching bundles for multiple Kibana instances

We're currently using Kibana 4.1.4 and run multiple instances off the same install folder with different reverse proxies in front. During pilot testing with 4.3 and 4.4 we've noticed it creates bundle files but doesn't use any unique identifier to save and serve them.

This means using our old system of spinning up instances fails as soon as a new process starts up or restarts. While they're "Optimizing and caching bundles for kibana and statusPage. This may take a few minutes" they are trouncing on the same bundle another process are using. The only workaround so far has been to have a folder per instance in /opt which is less than ideal.

  1. Is there a way to disable this optimizing process (likely not based on Disabling Kibana source optimization)?

  2. Is there a way to get instances to coexist using the same /opt/kibana folder?

Github issue exists which would resolve this issue