Skip to content

docs: remove obsolete Eagle3 prefix caching limitation #4436

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.

Sign up for GitHub

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

Open
michalzx wants to merge 1 commit into
base: releases/2026/3
Choose a base branch
from
+0 −1
Open

docs: remove obsolete Eagle3 prefix caching limitation #4436

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion demos/continuous_batching/speculative_decoding/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,6 @@ The built-in fallback is `5`. The same applies to `assistant_confidence_threshol
Eagle3 deployments currently have following known limitations:
- stateful mode (pipeline_type: LM) not supported,
- concurrency not supported - max 1 request can be processed at a time (**ALWAYS** use rest_workers=2 when deploying Eagle3 pipeline),
- prefix caching not supported,
- only greedy sampling is supported (enforced by OVMS if pipeline configured properly),
- MoE models not supported

Expand Down