Storing model weights at lower numerical precision to cut memory and speed up inference, trading a little accuracy for a lot of resource.
Running a trained model to get an output — as opposed to training, which is producing the model in the first place.
Inference is using a model rather than creating one. Training happens once and costs a great deal; inference happens on every request and is where nearly all cumulative cost ends up for a deployed system.
Inference is dominated by memory bandwidth rather than raw compute — the weights have to be read for every token generated — which is why quantisation, batching and caching matter so much more in production than they do in a notebook.
Storing model weights at lower numerical precision to cut memory and speed up inference, trading a little accuracy for a lot of resource.
A database built to store embeddings and find the nearest ones fast, which is what makes semantic search practical at scale.
Training a small model to imitate a large one, keeping most of the capability at a fraction of the cost.
Definitions are reviewed by our editorial team. Spotted a problem? Tell us.