Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.17] Updates LLM performance matrix (backport #6268) #6278

Merged
merged 2 commits into from
Dec 5, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Dec 5, 2024

Fixes #5950 — updates the LLM performance matrix

Preview: LLM Performance matrix (ESS) (Serverless)


This is an automatic backport of pull request #6268 done by Mergify.

* Updates LLM performance matrix

* fixes format

* Updates serverless version

* Excellent to great

(cherry picked from commit 8e29c53)

# Conflicts:
#	docs/serverless/AI-for-security/llm-performance-matrix.asciidoc
@mergify mergify bot requested a review from a team as a code owner December 5, 2024 18:14
Copy link
Contributor Author

mergify bot commented Dec 5, 2024

Cherry-pick of 8e29c53 has failed:

On branch mergify/bp/8.17/pr-6268
Your branch is up to date with 'origin/8.17'.

You are currently cherry-picking commit 8e29c537.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/AI-for-security/llm-performance-matrix.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/AI-for-security/llm-performance-matrix.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link

github-actions bot commented Dec 5, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@benironside
Copy link
Contributor

run docs-build

@benironside benironside merged commit 9b3eb3d into 8.17 Dec 5, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant