‍Overview:

Solsta updates environments in one step by scanning the local files and downloads only the changed data.
If Deltas are available, Solsta downloads only the modified parts of files between two releases instead of full files.

‍‍

What Are Deltas

Deltas are byte-level differences between two releases (for example, 1.0 → 1.1).
They reduce download size but require extra processing time during deployment.

‍‍

Do You Need Them?

Usually no.
Deltas help when bandwidth is limited, but most teams with fast internet or a local cache server gain little benefit.
Creating deltas can slow your CI/CD jobs, so use them only if network performance is a real issue.

‍‍

How They Work

• Controlled at the Environment level with the Update Path Count setting.
• This defines how many previous releases Solsta compares when creating deltas.
  • 0 = No deltas
  • 2 = Two delta paths (for example, 1.0→3.0 and 2.0→3.0)
• View existing deltas under Product → Environment → Repository → Update Paths.

‍‍

When They’re Created

Deltas generate automatically during Deploy or Promote if the environment’s Update Path Count > 0.
They’re built in Solsta’s cloud service and can add time to your pipeline while processing.

‍‍

If You Don’t Use Deltas

Solsta still updates efficiently using built-in data deduplication, usually fast enough for studio networks.

‍‍

Cleanup

Old deltas and unused data are removed automatically during the Solsta Cleanup step in your CI/CD tool.

In short: Deltas minimize downloads, not update time. Most users don’t need them. Configure only if bandwidth is limited.

‍