【Design Questinon】any plan to decouple batching and cache from llama?
Open
backlog
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 748
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 54
Description
Is there any reason why the batching and cache manager are implemented inside llama? Those looks generic functionalities, and better not mixed with the llama code. It looks misleading that turbomind only supports llama.
And is there any plan the abstract and decouple those functionalities from llama?
Contributor guide
Assessment
This issue has not been assessed yet.