We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I was curious if seamless integration with TF Serving is on the roadmap?
I see that there is support for remote models here remote_model.py, but is there anything beyond that we can look forward to?
We usually have a model server running that serves our models, so it would be great to reuse the models and resources allocated to the model server.
Thanks!
The text was updated successfully, but these errors were encountered:
It's on the roadmap to have more "seamless" integration with more frameworks, including TensorFlow Serving, but no ETA yet.
That being said: for a specific model, if you have a Python class that can call the model server, it should be fairly easy to map the flat dict format of PredictRequest/PredictResponse onto LIT types (see https://github.com/PAIR-code/lit/blob/main/docs/python_api.md#models).
Sorry, something went wrong.
Merge pull request #6 from PAIR-code/dev
99105f7
Use more sensible default values for settings in the clustering module.
No branches or pull requests
Hi,
I was curious if seamless integration with TF Serving is on the roadmap?
I see that there is support for remote models here remote_model.py, but is there anything beyond that we can look forward to?
We usually have a model server running that serves our models, so it would be great to reuse the models and resources allocated to the model server.
Thanks!
The text was updated successfully, but these errors were encountered: