After 100+ comments discussions here are quite difficult to read.
So some kind of automatic summary of the popular discussions would be great.
Somebody already did it: https://extraakt.com/
P.S. I am not the author: just found the link in the Llama 4 thread.
Well, the categories I use - do not overlap at all with the list of 1092 categories in Google Content Categories.
> it handles other classifications as well
hm... I highly doubt that.
First of all - I do not see API to upload list of MY categories.
Second: Can somebody with Google Cloud account try it?
I have no account and when creating it - it asks for credit card...
These are essentially function calls for you to run pre-trained models. If you want to continue this conversation elsewhere, feel free to shoot me an e-mail. It’s just my username @ gmail.
Well, looking at Triton Inference Server + OpenVINO backend [1]...uff... as you said: "significant amount of development effort". Not easy to handle when you do it first time.
Is ONMX runtime + OpenVINO [2] a good idea ?
Seems easier to install and to use: Pre-built Docker image and Python package...
Not sure about performance (the hardware-related performance improvements - they are in OpenVINO anyway, right?).
Hah, it actually gets worse. What I was describing was the Triton ONNX backend with the OpenVINO execution accelerator[0] (not the OpenVINO backend itself). Clear as mud, right?
Your issue here is model performance with the additional challenge of offering it over a network socket across multiple requests and doing so in a performant manner.
Triton does things like dynamic batching[1] where throughput is increased significantly by aggregating disparate requests into one pass through the GPU.
A docker container for torch, ONNX, OpenVINO, etc isn't even natively going to offer a network socket. This is where people try to do things like rolling their own FastAPI API implementation (or something) only to discover it completely falls apart at any kind of load. That's development effort as well but it's a waste of time.
The per-hour pricing I mentioned is fixed for the micro instance. (Well... It can go lower :-) ) I'm taking about normal EC2 instances here, so that is a cx11 alternative.
P.S. I am not the author: just found the link in the Llama 4 thread.