Commit Graph

5 Commits

Author SHA1 Message Date
Nikita 21fce9ba0d
feat: Tiktoken support (#6460)
Signed-off-by: Nikita Sukharev <kaonael@gmail.com>
2026-02-25 12:46:47 -08:00
Graham King b1186aee63
fix: Handle invalid JSON in config.json (#3043)
Signed-off-by: Graham King <grahamk@nvidia.com>
2025-09-15 23:30:34 +00:00
Graham King 183f2b3286
feat(dynamo-run): Allow setting KV cache block size (#1175)
Example:
```
dynamo-run out=<engine> <model> --kv-cache-block-size 64
```

In a distributed system this goes on the worker node and is propagated to ingress via the model deployment card.

Previously hard coded to 16, which is now the default.

- Load context_length from model. Closes #1172
- Store context length and KV cache block size in Model Deployment Card #1170
2025-05-22 14:55:36 -07:00
Graham King ceaeba3e38
feat: Qwen3, Gemma3 and Llama4 support (#1002)
. New mistralrs and llamacpp version
. mistralrs: Handle Gemma 3 and Llama 4 as vision models
. Update the dynamo-run docs to use Qwen 3
. Our pre-processor now supports Llama 4's newer multi-modal `config.json`
. Upgrade minijinja to handle Qwen 3's prompt template

For Llama 4 we'll need to limit the max seq len. vllm says:
> To serve at least one request with the models's max seq len (10485760), (240.00 GiB KV cache is needed,...

I was able to run Llama 4 with llamacpp and a quantized GGUF, with Dynamo doing the pre-processing.
2025-05-08 18:18:40 -04:00
Neelay Shah 08fcd7e93b refactor: move libs to lib dir
Signed-off-by: Neelay Shah <neelays@nvidia.com>
Co-authored-by: Ryan McCormick <rmccormick@nvidia.com>
2025-02-24 18:21:02 -08:00