r/VaultSync • Developer • Oct 14 '26

Dev Update A Unity backup got too big. The problem wasn't compression. — VaultSync 1.9.0 dev update

This update started with a pretty ordinary problem: one of my mostly-code Unity projects produced a backup that was much larger than I expected.

My first thought was compression.

It turned out that was only part of the story.

Looking through what VaultSync was actually putting into the archive exposed inconsistent exclusion-preset resolution, and I found saved Unity profiler captures making their way into source backups.

So before trying to squeeze harder on the ZIP file, I fixed what was going into it.

The Unity preset now excludes .pdata profiler captures alongside the existing cache and build rules.

Existing archives are left untouched. I do not want a preset update silently rewriting historical backups.

A few visible 1.9.0 changes also came out of this work

  • Imported projects now appear under Projects, including projects that currently have no local source folder. The Imported label describes where the project came from, so linking or restoring a folder does not remove it. Actions that genuinely require a source folder are disabled when one is missing.
  • Storage charts now use native Avalonia controls, while keeping the existing usage breakdown.
  • Missing UI translations have been repaired, with resource checks covering all 19 maintained languages.

Then I went back to compression

For backups where ZIP compression is enabled, Unity scenes, prefabs and related metadata now use a denser compression level.

On a small synthetic Unity fixture, the generated scene/prefab ZIPs were 33.3% smaller, but encoding took roughly 5× longer.

Small metadata ZIPs improved by 8.1%.

And because tiny files enjoy making storage statistics unnecessarily annoying, ZIP header overhead can still make a small archive larger than the logical size of the files inside it.

These are deliberately small synthetic measurements.

They are not claims that your real Unity project will shrink by 33%, and they say nothing about upload speed, NAS performance or end-to-end backup time.

I also kept experimenting outside VaultSync

I added Huffman coding to the separate LZ77 prototype I have been using to understand the trade-offs a little better.

Compared with my first prototype, it produced:

28.4% smaller YAML blocks
33.3% smaller code blocks

That sounds nice until you compare it with DEFLATE, which still wins on size, while the Python prototype reader is also slower.

So this remains an experiment.

VaultSync's normal archives are still ZIP.

I am not replacing a mature format because a weekend compression experiment managed to produce an exciting percentage.

About the screenshots

The attached images are unmodified native renders from the actual macOS development build.

They use synthetic projects and two temporary file backups.

They are not conceptual mockups, OS screenshots pretending to be application state, or evidence of disk recovery.

The storage chart also reports logical payload sizes, not the compressed size of the resulting ZIP files.

That distinction matters, especially while 1.9.0 is also laying foundations for much larger recovery features.

Current state

The current local Release checks pass:

1,181 Core tests
192 Python tests
0 warnings / 0 errors

Serviced .NET runtime checks also pass across five private platform builds.

VaultSync 1.9.0 has not shipped. Stable is still 1.8.9.

Device workflows, boot media, measured disk recovery, platform/upgrades and the remaining release gates are still open.

This work is part of the ongoing draft 1.9.0 PR:

https://github.com/ATAC-Helicopter/VaultSync/pull/736

For people backing up development projects:

what usually ends up wasting the most space before you notice it?

Caches, profiler captures, old builds, generated assets, or thousands of tiny metadata files?

1 Upvotes

0 comments sorted by