Skip to main content
Fine-tuning adapts a base model to your task using a LoRA (Low-Rank Adaptation) adapter. You configure a training run, BenchGen provisions the GPU and runs it, and you watch progress in real time until the adapter is ready to merge and save.

Prerequisites

  • A base model to fine-tune. You can pick one from your workspace, the public library, the platform, or HuggingFace.
  • A training dataset. See Add a dataset, or pick one from the library or HuggingFace.

Steps

1. Start a new training run

In the Train tab, click Jobs in the left sidebar to see your Training Jobs, with totals for running, completed, stopped, and failed runs. Click + New Training in the top right. The Training Jobs list with the New Training button

2. Name the run and pick a base model

Give the run a Training Name. This name is saved to the Knowledge API and reused as the default when you push the merged model to BenchGen later. Open the Base Model dropdown and choose a source:
SourceWhat it is
My ModelsModels already in your workspace.
Public LibraryModels shared by the community.
PlatformModels published on BenchGen.
HuggingFaceAny public model from the Hub. Search by name.
The New Training form with the base model, dataset, and LoRA configuration The base model dropdown showing the four sources To use a model that isn’t already in your workspace, switch to the HuggingFace tab and search the Hub by name. Each result shows its download count, likes, and task tag. Click one to select it as the base model. Searching HuggingFace for a base model

3. Choose a dataset

Open the Dataset dropdown and pick from My Datasets, Public Library, Fine-tune Datasets (datasets exported from Eval runs), or HuggingFace. The dataset dropdown showing the available sources The HuggingFace tab works the same way for datasets. Search the Hub and pick any public dataset by name. Searching HuggingFace for a dataset

4. Configure the LoRA parameters

ParameterRangeDefaultWhat it controls
Rank (r)4–648Adapter capacity.
Alpha4–12816Scaling factor. A common ratio is Alpha = 2 × rank.
Dropout0.0–0.50.05Regularization.
Learning Rate1e-5 to 5e-41e-4Step size for gradient updates.
The Quick Tips panel sums up sensible defaults: rank 8–16 works well for most tasks, Alpha = 2 × rank is a good ratio, 50–100 steps is enough for a quick validation run, and a lower learning rate gives more stable convergence.

5. (Optional) Adjust advanced options

Expand Advanced Options for finer control:
SettingDefaultNotes
QuantizationFull PrecisionEquivalent to Q4/Q8 in GGUF, but for training. Use a lower precision for large models when VRAM is limited.
Epochs2Full passes over the dataset.
Batch Size4Examples per gradient step.
Max Steps50Caps the run. Set -1 or click Full to train over the entire dataset.
Auto GPU SelectionOnLets the backend pick the first compatible free GPU or accelerator from the Ray cluster.
The Training Summary panel on the right updates as you change settings. It shows the estimated steps and time, so capping at 50 steps reads as a quick run, while Full estimates a longer one. Advanced options expanded, with quantization, epochs, batch size, and max steps Max Steps set to Full, with the summary showing the longer estimate

6. Start training

Click Start Training. The job opens to its detail page with a status of Training. The job detail page just after training starts

7. Monitor progress

The Training Progress card streams the current step and percent complete, along with elapsed time, ETA, speed (it/s), epoch, loss, learning rate, and gradient norm. Expand Training Logs for the raw output, or click Cancel Training if you need to stop early. Training in progress with live metrics

8. Training completes

When the run finishes, the status changes to Completed and the progress card shows Finished with the final loss and runtime. The Actions panel unlocks so you can download the adapter or merge and save the model. A completed training run with the Actions panel unlocked

Next Steps

Training is complete and the adapter is ready. Merge it into the base model and push it to BenchGen so you can run and evaluate it.

Merge & save the model

Combine the adapter with the base model and save it to the platform.

Run inference

Test the adapter in a chat interface before merging.