Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Disable bfetch in serverless (#183096)
## Summary Part of #181938. Disables bfetch in serverless by overriding the `bfetch:disable` advanced setting in the serverless.yml. Bfetch was introduced to bypass the browser connection limit when multiple search requests are made. Here's a picture of what the network tab looks like with bfetch turned off in http1: ![image](https://github.com/elastic/kibana/assets/1178348/40e156d1-1dc8-4a03-9d1d-cc6c1d61134e) As the number of requests reaches the connection limit (6 on most modern browsers), requests stall until a connection is available. In Cloud/serverless, we have a http2 proxy. Http2 does not have this browser connection limit. Turning off bfetch allows us to collect metrics to decide if we want to remove it altogether: | Bfetch enabled | Bfetch disabled (this PR) | | --------------- | ------------------------- | | ![image](https://github.com/elastic/kibana/assets/1178348/09c0673a-573f-422a-b95d-4fa1adcc08b5) | ![image](https://github.com/elastic/kibana/assets/1178348/0a44f8a4-d047-4b93-afc4-3fdb8a83b494) | In my tests, the overall time for a sample dashboard to load was actually smaller with bfetch disabled on http2 vs. bfetch enabled. ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
- Loading branch information