---
title: "2026-08-25 vxData storage call collapse review"
description: "Reviewed the SDK-to-API storage call graph for safe removal of duplicate transfer calls."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-08-25 vxData storage call collapse review

## Work Done

- Reviewed branch `alex.leake/feat/s3-optimisations` without editing the monorepo.
- Traced upload, download, open, materialize, DataFrame upload, transport, Direct S3, and API route/service calls.
- Identified safe batching and deduplication opportunities in artefact downloads, dictionary materialization, and DataFrame uploads.

## Lessons Learned: Pitfalls

- The general infrastructure SOPs did not contain branch-specific transfer design details; the package README and code were authoritative.
- Public API compatibility can make apparently dead route removal uncertain, so findings were restricted to duplicated calls with unchanged output contracts.

## Lessons Learned: Improvements

- A short vxData storage call-graph note that names batching boundaries would make future transfer reviews faster.

Source: https://docs.virdx.dev/knowledge/inbox/2026-08-25-infrastructure-vxdata-storage-call-collapse-review/index.mdx