Scope
Language rewrites are a much simpler endeavor with the advent of vibezzzz powered software generation.
We should consider rewriting this repo in Rust as a scheduler will have to handle a high volume of requests, and so multi-threading will be highly preferred. Rust allows us to avoid the GIL and avoid hitting performance bottlenecks.
The Py-bindings will be straightforward and performant. This is a common pattern followed by libs that require high performance (the core pytorch libs are in C/C++).
The reason we care to stay Python-adjacent is b/c this repo is intended to be able to run natively in a Ray/Slurm, or other Py-native environ.
Why
The purpose of this issue is to capture historical precedence & decision to move forward with the language change.
Scope
Language rewrites are a much simpler endeavor with the advent of vibezzzz powered software generation.
We should consider rewriting this repo in Rust as a scheduler will have to handle a high volume of requests, and so multi-threading will be highly preferred. Rust allows us to avoid the GIL and avoid hitting performance bottlenecks.
The Py-bindings will be straightforward and performant. This is a common pattern followed by libs that require high performance (the core pytorch libs are in C/C++).
The reason we care to stay Python-adjacent is b/c this repo is intended to be able to run natively in a Ray/Slurm, or other Py-native environ.
Why
The purpose of this issue is to capture historical precedence & decision to move forward with the language change.