1. 15 Sep, 2025 1 commit
  2. 05 Sep, 2025 1 commit
  3. 04 Sep, 2025 1 commit
  4. 03 Sep, 2025 3 commits
  5. 29 Aug, 2025 2 commits
  6. 28 Aug, 2025 2 commits
  7. 27 Aug, 2025 1 commit
  8. 26 Aug, 2025 1 commit
  9. 25 Aug, 2025 2 commits
  10. 22 Aug, 2025 2 commits
  11. 21 Aug, 2025 1 commit
  12. 20 Aug, 2025 1 commit
  13. 19 Aug, 2025 2 commits
  14. 18 Aug, 2025 1 commit
  15. 15 Aug, 2025 1 commit
  16. 13 Aug, 2025 2 commits
  17. 12 Aug, 2025 1 commit
  18. 07 Aug, 2025 2 commits
  19. 01 Aug, 2025 1 commit
  20. 18 Jul, 2025 1 commit
  21. 17 Jul, 2025 1 commit
  22. 15 Jul, 2025 1 commit
  23. 10 Jul, 2025 1 commit
  24. 01 Jul, 2025 2 commits
  25. 26 Jun, 2025 1 commit
  26. 06 Jun, 2025 1 commit
  27. 04 Jun, 2025 2 commits
  28. 22 May, 2025 2 commits
    • Graham King's avatar
      feat(dynamo-run): Allow setting KV cache block size (#1175) · 183f2b32
      Graham King authored
      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
      183f2b32
    • Graham King's avatar
      fix: Fix race condition in kv_router unit test (#1174) · 3bde1e45
      Graham King authored
      Removed the hard coded sleeps, explained what we're testing.
      
      Closes https://github.com/ai-dynamo/dynamo/issues/1132
      
      The race condition is that `apply_event` sends a message on a channel, it does not directly apply the event. At some later point the tokio runtime schedules the task running the channel receiver, which applies the event. If that had not happened yet the test would fail.
      3bde1e45