1. 22 Jul, 2025 1 commit
  2. 18 Jul, 2025 2 commits
  3. 17 Jul, 2025 3 commits
  4. 16 Jul, 2025 2 commits
  5. 15 Jul, 2025 3 commits
  6. 10 Jul, 2025 1 commit
  7. 09 Jul, 2025 1 commit
  8. 08 Jul, 2025 1 commit
  9. 07 Jul, 2025 2 commits
  10. 03 Jul, 2025 1 commit
  11. 01 Jul, 2025 1 commit
  12. 24 Jun, 2025 3 commits
  13. 21 Jun, 2025 1 commit
  14. 17 Jun, 2025 1 commit
  15. 13 Jun, 2025 2 commits
  16. 11 Jun, 2025 2 commits
  17. 09 Jun, 2025 1 commit
  18. 04 Jun, 2025 1 commit
  19. 03 Jun, 2025 1 commit
  20. 29 May, 2025 2 commits
  21. 23 May, 2025 2 commits
  22. 22 May, 2025 2 commits
    • Graham King's avatar
      feat(dynamo-run): Allow setting context-length (#1157) · 6d5da821
      Graham King authored
      Llama 4 has a very large context length (aka n_ctx, model_max_length, max_model_len), and vllm won't start unless it can allocate enough KV cache for the entire context.
      
      Allow passing `--context-length <N>` to `dynamo-run` to limit it so long-context models will fit.
      
      Future todo:
      - Restrict every request's `max_tokens` to below the context length. Our pre-processor should do this by setting stop_conditions.max_tokens. mistralrs engine wrapper must do it itself because it does not use the pre-processor.
      - mistralrs and llamacpp currently have a hard-coded max context length if one is not provided on the command line. Change those to be the model's built-in max, read from the GGUF or tokenizer_config.json.
      6d5da821
    • jmswen's avatar
  23. 21 May, 2025 2 commits
  24. 20 May, 2025 1 commit
    • Faradawn Yang's avatar
      chore: Remove unused RouterType and ModelMetaData (#1138) · eb821bee
      Faradawn Yang authored
      Remove RouterType and ModelMetaData in `lib/runtime/src/protocols.rs`, which are unused (no outside reference). It is because that the routing has been moved to its own module, `pipeline/network/egress/push_router.rs`. Therefore, the legacy definition of RouterType in `protocols.rs` is no longer used.
      eb821bee
  25. 19 May, 2025 1 commit
    • Graham King's avatar
      feat: Support multiple models on single ingress node (#1127) · aeb79e62
      Graham King authored
      We can now do this:
      
      - Node 1:
      
      ```
      dynamo-run in=http out=dyn
      ```
      
      - Node 2 and 3, two instances of component 'backend' in the nemotron_ultra pipeline:
      
      ```
      dynamo-run in=dyn://nemotron_ultra.backend.generate out=vllm /data/models/NemotronUltra
      ```
      
      - Node 4 and 5, two instances of the 'backend' component in nemotron_super pipeline:
      
      ```
      dynamo-run in=dyn://nemotron_super.backend.generate out=vllm /data/models/NemotronSuper
      ```
      
      The ingress node will discover all four instances and route correctly. We have been planning for this for a long time now.
      
      As part of this auto-discovery is now always `out=dyn`, with no extra URL parts. Previously it could only route to a single pipeline.
      
      Also:
      - Refactor endpoint / instance naming now that I understand them
      - Fix removing models when their instance stops.
      aeb79e62