How Does VLM Training Work?
Learn how vision-language model training works in Datature Vi. Understand epochs, batch size, learning rate, loss curves, overfitting, and validation splits in plain language.
Training a VLM means showing the model your annotated images repeatedly until it learns the patterns in your data. Datature Vi handles the GPU infrastructure. You configure the model, select your dataset, set a few training parameters, and launch. This page explains what happens during training and what each setting controls.
What happens during a training run?
During training, Datature Vi feeds your annotated images through the model in small groups. The model tries to predict the correct output for each image, checks how far off it was, and adjusts its internal parameters to do better next time. This cycle repeats thousands of times.
After training completes, you get a trained model you can download and run inference on. See Train a Model for the full step-by-step guide.
Training settings explained
You don't need to change most settings for your first run. Here's a quick reference, with details below.
For your first training run, the defaults work well. See Model Settings when you're ready to tune.
How do training settings interact?
Training settings do not work in isolation. Changing one often affects how others behave. Here are the interactions that matter most.
Batch size and learning rate
Batch size and learning rate are linked. A larger batch means the model averages gradients over more images, which smooths out noise. This smoother signal can handle a slightly higher learning rate. A smaller batch produces noisier gradients, so a lower learning rate works better.
The rule of thumb: if you double the batch size, you can try increasing the learning rate by 1.4x (the square root of 2). If you halve the batch size, reduce the learning rate by a similar factor.
In practice, leave the learning rate at the default unless you see instability. Adjust batch size first to fix memory issues, and only change the learning rate if loss curves look abnormal.
Epochs and dataset size
Smaller datasets need more epochs because the model sees fewer unique examples per pass. A dataset of 50 images at 200 epochs means the model sees each image 200 times. A dataset of 5,000 images at 20 epochs gives the model enough variety per pass that it does not need as many repetitions.
The risk with high epoch counts on small datasets is overfitting. The model starts memorizing individual images rather than learning reusable patterns. Watch your validation loss: if it climbs while training loss keeps falling, you have gone too far.
Model size and data requirements
Larger models have more parameters, which gives them more capacity to learn. But that capacity is wasted without enough data. A 32B model trained on 50 images will overfit faster than a 4B model on the same data, because the larger model has so many parameters that it can memorize small datasets more easily.
Match model size to data size. For datasets under 200 images, start with a 2B-4B model. For 200-1,000 images, a 7B-9B model works well. Scale to 27B+ only when you have 1,000+ annotated images.
How to read loss curves
The loss curve shows how fast the model's errors decrease over time. Orange represents training loss (calculated at every step). Blue represents validation loss (calculated at evaluation intervals).
Overfitting means the model has memorized the training examples rather than learning reusable patterns. It performs well on images it has seen but poorly on new ones. The fix is more data, fewer epochs, or both.
Underfitting means the model hasn't learned enough. It performs poorly on both training and new images. The fix is more training time or a larger model architecture.
When training goes wrong
Training does not always converge on the first attempt. Here are the most common failure patterns and what causes them.
Hardware and compute
Training requires GPUs. Datature Vi manages the infrastructure so you don't need to provision or configure hardware yourself. You select a GPU tier based on your model size and training mode.
Training consumes Compute Credits from your organization's plan. You can monitor your usage and remaining Compute Credits in Resource Usage.
Frequently asked questions
Further reading
- How to Interpret Training Graphs -- A practical guide to reading loss curves and other training charts.
- Fine-tuning glossary -- Quick reference for the fine-tuning process.
Related resources
Updated 3 months ago
