(no title)
daniel-thompson | 1 year ago
The article outlines some interesting ways to evade this problem. What's the latest thinking on robustly addressing it, e.g. are there any approaches for executing inference on a tf or pytorch model from within a golang process, no sidecar required?
kevmo314|1 year ago
Practically speaking though, the rate at which models change is so fast that if you opt to go this route, you'll perpetually be lagging behind the state of the art by just a bit. Either you'll be the one implementing the latest improvements or be waiting for the framework to catch up. This is the real value of the sidecar approach: when a new technique comes out (like speculative decoding, for example) you don't need to reimplement it in Go but instead can use the implementation that most other python users will use.
neomantra|1 year ago
[1] https://github.com/gomlx/gomlx
[2] https://github.com/janpfeifer/gonb
eliben|1 year ago
richardjennings|1 year ago
uriah|1 year ago
pjmlp|1 year ago