-
Couldn't load subscription status.
- Fork 184
Add non-streaming response to approximate prefix cache. #1719
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zetxqx The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
e21b3fe to
565a1ce
Compare
a7ddc30 to
7476ad3
Compare
e1f9e73 to
eec941c
Compare
|
/assign @liu-cong |
…ormat for plugins
…ethod of Messages in ChatCompletions.
eec941c to
824af68
Compare
|
@zetxqx: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add non streaming response to prefix cache, several points to pay attention:
requestcontrolplugin into 3 separate plugins to add streamed request functionality #1661ResponseCompleteto accept a*types.LLMResponsewhich has richer structure.ChatCompletionsmessages for prefix caching is now standardized viaMarshalMessagesToJSONto improve caching accuracy for multi-turn conversations.Which issue(s) this PR fixes:
Fixes Partially #971
Does this PR introduce a user-facing change?: