# Backport
This will backport the following commits from `main` to `8.17`:
- [[Performance][Security Solution][1/4] - Field Browser Performance
(#212469)](https://github.com/elastic/kibana/pull/212469)
<!--- Backport version: 9.6.6 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)
<!--BACKPORT [{"author":{"name":"Michael
Olorunnisola","email":"michael.olorunnisola@elastic.co"},"sourceCommit":{"committedDate":"2025-03-04T01:22:25Z","message":"[Performance][Security
Solution][1/4] - Field Browser Performance (#212469)\n\n## Summary\nPart
1 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor
setup see testing section
here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas
to test:**\n- Alert Table (Alerts, Rule Detail, Rule Preview pages)\n-
Security solution field browser component\n- Flyout table tab.\n\n###
Background\n\nWhen investigating the performance of the security
solution application,\none of the issues that was observed was locking
of the page and field\nbrowser component when the total number of fields
returned were\nsignificantly high.\n\nThis led to cell values not
rendering in the alert table, and the field\nbrowser in all the security
solution pages causing the page to crash.\nThe relevant images can be
seen at the bottom of this description\n\nIn short: The
`push(...fields)` is non-performant at scale, and at a\nsignificant
enough scale (Testing was done with 500k mapped fields),\nfails to run
due to excessive arguments provided to the `push` method.\nIn this PR
improvements are made in the `browserFields` transformations\nthat are
done for the field browser component, expandable flyout table\ntab, and
alert/rule tables via `CellValue` component.\n\nThis work was done to
get immediate improvements in the security\nsolution UI, but a longer
term consideration will be whether or not the\n`browserFields` is even
necessary anymore as a concept based on what is\navailable via the
`fields` api. We will revisit once our Sourcerer\nrefactoring work is
done.\n\n<img width=\"1728\" alt=\"Screenshot 2025-02-26 at 10 15
29 AM\"\nsrc=\"https://github.com/user-attachments/assets/a25f577f-f758-415e-9c93-5452eadb8020\"\n/>\n\n<img
width=\"1445\" alt=\"Screenshot 2025-02-26 at 10 18
36 AM\"\nsrc=\"https://github.com/user-attachments/assets/d70970d3-991a-47ba-b617-5862d18101b6\"\n/>\n\n<img
width=\"1469\" alt=\"Screenshot 2025-02-26 at 10 19
48 AM\"\nsrc=\"4dff2378-d61b-4770-b46b-41cb37d6ead4)\n\n\n###
After the fix\n(Done on [this
branch](https://github.com/elastic/kibana/pull/212173)\nthat has the
other changes as
well)\n\n\nhttps://github.com/user-attachments/assets/da992296-4eb8-49d4-96ca-b0a19a00f1f0\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"750e156c26078015025551c4f10d299ba269fa35","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat
Hunting","Team:Threat
Hunting:Investigations","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"[Performance][Security
Solution][1/4] - Field Browser
Performance","number":212469,"url":"https://github.com/elastic/kibana/pull/212469","mergeCommit":{"message":"[Performance][Security
Solution][1/4] - Field Browser Performance (#212469)\n\n## Summary\nPart
1 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor
setup see testing section
here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas
to test:**\n- Alert Table (Alerts, Rule Detail, Rule Preview pages)\n-
Security solution field browser component\n- Flyout table tab.\n\n###
Background\n\nWhen investigating the performance of the security
solution application,\none of the issues that was observed was locking
of the page and field\nbrowser component when the total number of fields
returned were\nsignificantly high.\n\nThis led to cell values not
rendering in the alert table, and the field\nbrowser in all the security
solution pages causing the page to crash.\nThe relevant images can be
seen at the bottom of this description\n\nIn short: The
`push(...fields)` is non-performant at scale, and at a\nsignificant
enough scale (Testing was done with 500k mapped fields),\nfails to run
due to excessive arguments provided to the `push` method.\nIn this PR
improvements are made in the `browserFields` transformations\nthat are
done for the field browser component, expandable flyout table\ntab, and
alert/rule tables via `CellValue` component.\n\nThis work was done to
get immediate improvements in the security\nsolution UI, but a longer
term consideration will be whether or not the\n`browserFields` is even
necessary anymore as a concept based on what is\navailable via the
`fields` api. We will revisit once our Sourcerer\nrefactoring work is
done.\n\n<img width=\"1728\" alt=\"Screenshot 2025-02-26 at 10 15
29 AM\"\nsrc=\"https://github.com/user-attachments/assets/a25f577f-f758-415e-9c93-5452eadb8020\"\n/>\n\n<img
width=\"1445\" alt=\"Screenshot 2025-02-26 at 10 18
36 AM\"\nsrc=\"https://github.com/user-attachments/assets/d70970d3-991a-47ba-b617-5862d18101b6\"\n/>\n\n<img
width=\"1469\" alt=\"Screenshot 2025-02-26 at 10 19
48 AM\"\nsrc=\"4dff2378-d61b-4770-b46b-41cb37d6ead4)\n\n\n###
After the fix\n(Done on [this
branch](https://github.com/elastic/kibana/pull/212173)\nthat has the
other changes as
well)\n\n\nhttps://github.com/user-attachments/assets/da992296-4eb8-49d4-96ca-b0a19a00f1f0\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"750e156c26078015025551c4f10d299ba269fa35"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212469","number":212469,"mergeCommit":{"message":"[Performance][Security
Solution][1/4] - Field Browser Performance (#212469)\n\n## Summary\nPart
1 of https://github.com/elastic/kibana/pull/212173\n\n### Testing\nFor
setup see testing section
here:\nhttps://github.com/elastic/kibana/pull/212173#issue-2870522020\n\n**Areas
to test:**\n- Alert Table (Alerts, Rule Detail, Rule Preview pages)\n-
Security solution field browser component\n- Flyout table tab.\n\n###
Background\n\nWhen investigating the performance of the security
solution application,\none of the issues that was observed was locking
of the page and field\nbrowser component when the total number of fields
returned were\nsignificantly high.\n\nThis led to cell values not
rendering in the alert table, and the field\nbrowser in all the security
solution pages causing the page to crash.\nThe relevant images can be
seen at the bottom of this description\n\nIn short: The
`push(...fields)` is non-performant at scale, and at a\nsignificant
enough scale (Testing was done with 500k mapped fields),\nfails to run
due to excessive arguments provided to the `push` method.\nIn this PR
improvements are made in the `browserFields` transformations\nthat are
done for the field browser component, expandable flyout table\ntab, and
alert/rule tables via `CellValue` component.\n\nThis work was done to
get immediate improvements in the security\nsolution UI, but a longer
term consideration will be whether or not the\n`browserFields` is even
necessary anymore as a concept based on what is\navailable via the
`fields` api. We will revisit once our Sourcerer\nrefactoring work is
done.\n\n<img width=\"1728\" alt=\"Screenshot 2025-02-26 at 10 15
29 AM\"\nsrc=\"https://github.com/user-attachments/assets/a25f577f-f758-415e-9c93-5452eadb8020\"\n/>\n\n<img
width=\"1445\" alt=\"Screenshot 2025-02-26 at 10 18
36 AM\"\nsrc=\"https://github.com/user-attachments/assets/d70970d3-991a-47ba-b617-5862d18101b6\"\n/>\n\n<img
width=\"1469\" alt=\"Screenshot 2025-02-26 at 10 19
48 AM\"\nsrc=\"4dff2378-d61b-4770-b46b-41cb37d6ead4)\n\n\n###
After the fix\n(Done on [this
branch](https://github.com/elastic/kibana/pull/212173)\nthat has the
other changes as
well)\n\n\nhttps://github.com/user-attachments/assets/da992296-4eb8-49d4-96ca-b0a19a00f1f0\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common
scenarios","sha":"750e156c26078015025551c4f10d299ba269fa35"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
543bf80673