Skip to content

Update docs - #4432

Open
mzegla wants to merge 3 commits into
mainfrom
llm_reference_update
Open

Update docs#4432
mzegla wants to merge 3 commits into
mainfrom
llm_reference_update

Conversation

@mzegla

@mzegla mzegla commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Copilot AI lite review requested due to automatic review settings August 5, 2026 14:36

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates documentation for OpenVINO Model Server’s generative/model configuration, expanding guidance around automatic task/device detection and extending LLM reference docs with Omni-related and chat-template behavior details.

Changes:

  • Clarifies/extends CLI documentation for --task and --target_device, and adds new sections describing automatic task detection and automatic target device detection.
  • Updates LLM reference documentation to include Omni servable type notes, additional parser names, and extra /chat/completions behavior details.
  • Minor formatting/wording adjustments across the updated docs.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
docs/parameters.md Adds/updates CLI parameter descriptions and new sections for automatic task/device detection.
docs/llm/reference.md Updates LLM reference to include Omni servable, parser lists, and additional chat-template/tooling notes.
Suppressed comments (1)

docs/parameters.md:107

  • This --target_device row lists MULTI and omits NPU/AUTO/GPU.<index>, but the server’s generative text generation flow validates target_device against CPU, GPU, NPU, AUTO (plus GPU.<index> and AUTO:/HETERO: prefixes). As written, the docs suggest some unsupported values and hide supported ones.
| `--target_device`           | `string`     | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"MULTI"/"HETERO"`. If not specified, auto-detected based on available devices. |

Comment thread docs/parameters.md Outdated
| `--task` | `string` | Task type for the model (`text_generation`, `embeddings`, `rerank`, `image_generation`, `text2speech`, `speech2text`). |
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"NPU"/"MULTI"/"HETERO"`. |
| `--task` | `string` | Task type for the model (`text_generation`, `embeddings`, `rerank`, `image_generation`, `text2speech`, `speech2text`). If not specified, automatically inferred from model metadata. |
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"NPU"/"MULTI"/"HETERO"`. If not specified, auto-detected based on available devices. |
Comment thread docs/parameters.md Outdated
Comment thread docs/llm/reference.md Outdated
Comment thread docs/parameters.md Outdated
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"MULTI"/"HETERO"` |
| `--task` | `string` | Task type the model will support (`text_generation`, `embeddings`, `rerank`, `image_generation`, `text2speech`, `speech2text`). |
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"MULTI"/"HETERO"`. If not specified, auto-detected based on available devices. |
| `--task` | `string` | Task type the model will support (`text_generation`, `embeddings`, `rerank`, `image_generation`, `text2speech`, `speech2text`). If not specified, automatically inferred from model metadata. |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe there should be links to Automatic task detection and Automatic target device detection sections

Comment thread docs/llm/reference.md

### Visual Language servable limitations
- works only on `/chat/completions` endpoint,
- user-supplied `<ov_genai_image_N>` placeholder strings in message content are rejected — these are reserved for internal image injection by the server,

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are they still used?

Comment thread docs/llm/reference.md
- **[NPU only]** requests MUST include one and only one image in the messages context. Other request will be rejected.

## References
- [Chat Completions API](../model_server_rest_api_chat.md)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also reference to responses and tokenize?

Comment thread docs/parameters.md
| `"plugin_config"` | `json/string` | List of device plugin parameters. For full list refer to [OpenVINO documentation](https://docs.openvino.ai/2026/documentation/compatibility-and-support/supported-devices.html) and [performance tuning guide](./performance_tuning.md). Example: <br> `{"PERFORMANCE_HINT": "LATENCY"}` |
| `"nireq"` | `integer` | The size of internal request queue. When set to 0 or no value is set value is calculated automatically based on available resources.|
| `"target_device"` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"MULTI"/"HETERO"` |
| `"target_device"` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"MULTI"/"HETERO"`. |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `"target_device"` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"MULTI"/"HETERO"`. |
| `"target_device"` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"NPU"/"HETERO"/"`. By default server selects the device with this priority: dGPU if present, iGPU if present, CPU. If several discrete GPUs are present, the one with most free VRAM will be selected. |

Comment thread docs/parameters.md Outdated
| `--task` | `string` | Task type for the model (`text_generation`, `embeddings`, `rerank`, `image_generation`, `text2speech`, `speech2text`). |
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"NPU"/"MULTI"/"HETERO"`. |
| `--task` | `string` | Task type for the model (`text_generation`, `embeddings`, `rerank`, `image_generation`, `text2speech`, `speech2text`). If not specified, automatically inferred from model metadata. |
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"NPU"/"MULTI"/"HETERO"`. If not specified, auto-detected based on available devices. |

@dtrawins dtrawins Aug 5, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"NPU"/"MULTI"/"HETERO"`. If not specified, auto-detected based on available devices. |
| `--target_device` | `string` | Device name to be used to execute inference operations. Accepted values are: `"CPU"/"GPU"/"NPU"/"HETERO"`. If not specified, auto-detected based on available devices. |

Comment thread docs/parameters.md
## Automatic task detection

When `--task` is not provided, the server automatically infers the generative task from model metadata. Detection is performed by a chain of detectors with the following priority:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this logic is to complex to cover it in documentation. The code has this logic. Users don't need to care about those nuances in my opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants