Marc-André Bombeck 13ea849188 perf(backup): load the backup payload schema on first use ...

backupPayloadSchema is built when validations/backup.ts is evaluated and
holds about 12 MB of heap. The restore job, the stored-backup readers and
the export writer import that module, and they sit on the boot path, so
every server process built the schema at start whether or not it ever
touched a backup.

The schema version, the compatibility check and the per-section summary
move to validations/backup-summary.ts, which never builds the schema. The
call sites that validate a file (upload, restore, the summary and download
routes, and the streamed reader's element check) load backup.ts with a
dynamic import at that moment; everything else takes only types. The
OpenAPI registry keeps its static import, since only the spec generator
loads it.

After warm-up on a production build under --max-old-space-size=524, the
used heap drops by about 29 MB, and the schema no longer appears in a heap
snapshot. A structural test refuses a new static value import of the
module outside the registry.

2026-10-04 18:23:14 +02:00

..

fixtures

Merge remote-tracking branch 'origin/main' into ready/pr-1131

2026-10-04 14:08:27 +02:00

integration

perf(backup): load the backup payload schema on first use

2026-10-04 18:23:14 +02:00