Skip to content

Conversation

ChrisHegarty
Copy link
Contributor

Backports the following commits to 8.x:

This commit adds logging of the system's vector capability check, to help with diagnosing whether AVX2 or AVX 512 will be used.
@ChrisHegarty ChrisHegarty added :Search Relevance/Vectors Vector search >non-issue auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Dec 10, 2024
@elasticsearchmachine elasticsearchmachine merged commit eff40c1 into elastic:8.x Dec 10, 2024
15 checks passed
@ChrisHegarty ChrisHegarty deleted the backport/8.x/pr-118325 branch December 10, 2024 17:00
ChrisHegarty added a commit that referenced this pull request Dec 11, 2024
This commit adds logging of the system's vector capability check, to help with diagnosing whether AVX2 or AVX 512 will be used.
ChrisHegarty added a commit that referenced this pull request Dec 11, 2024
This commit adds logging of the system's vector capability check, to help with diagnosing whether AVX2 or AVX 512 will be used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >non-issue :Search Relevance/Vectors Vector search Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch v8.18.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants