Performance

When should you pre-cache project media in Suite?

Use Suite pre-caching to prepare known project media early while keeping the wider library available on demand.

Stream directly, and pre-cache only when it helps

Suite streams files directly from the cloud; you do not need to pre-cache media before working. Pre-caching is an optional optimization for known files when a particular session benefits from preparing them ahead of time. Start with direct streaming, then choose pre-caching only where it adds value. Suite remains a connected workflow in either case.

Suite's pre-cache guide documents selecting whole files or folders in advance. It also says selected folders update as their contents change. Suite still requires an internet connection, including workflows that use cached material.

Focus pre-caching on the next session

Start with the next useful activity: a review, a finishing pass, an analysis job or a handoff to another operator. Identify the actual media and dependencies needed for that activity. A narrow session with known inputs is a clearer preparation target than an unspecified request to make everything fast.

Include assets outside the obvious media folder when the application needs them. Record unresolved paths before the session so a missing dependency does not get mistaken for a storage-speed problem. Keep optional material separate from material required to start.

For an agent job, use the approved input list and expected execution window. Pre-caching unrelated files is not a substitute for knowing which data the task is allowed to read.

Make room for preparation and later changes

Review the selected media size, available local capacity and time before work begins. Leave space for application scratch and outputs. Selection alone is not evidence that preparation finished; inspect the supported client view and exercise the intended task before calling the session ready.

A changing folder needs extra attention. If new media arrives shortly before review, the earlier preparation may no longer describe the current set. Identify a content cutoff or recheck the changed inputs. Do not treat yesterday's observation as proof that today's new files are ready.

This is an operational readiness check, not a promised cache-completion API. If an unattended workflow needs a machine-readable signal, confirm the supported interface and its meaning with Suite.

Choose preparation by the kind of session

Exploratory work: An editor is browsing an uncertain set of shots. Begin with direct streaming, because preparing a large speculative set may transfer material the editor never uses. Observe the application’s actual behavior before choosing an optimization.

A defined finishing session: The timeline and dependencies are known. Optional preparation may be useful if a test shows that it improves the session and there is suitable local capacity. Record the exact input revision so later additions are not mistaken for already prepared material.

A full-input processing job: An agent or application will inspect all approved inputs. Compare starting the job directly with a separately prepared run, including both preparation and processing in the result. Moving the waiting earlier is useful only when it improves the actual schedule or experience.

These choices keep the benefit clear: the shared library is available through Suite, and deliberate pre-caching is an optional tool for a specific session. It is not an onboarding requirement or an offline mode.

Measure the whole session cost

Record preparation time separately from time spent waiting during useful work. A pre-cached demonstration should say that preparation occurred. Otherwise the comparison hides the work that made the session possible.

For a fair evaluation, run the same representative task under clearly recorded preparation conditions. Observe start-up, sustained use and any unexpected input changes. Report whether the preparation improved the part of the session that mattered, rather than labeling every difference as a product-wide speed improvement.

Keep pre-caching when predictable sessions benefit from the earlier preparation and the local resources are justified. Reconsider the selection when most prepared data goes unused or the working set changes too quickly. The goal is to make the next useful task ready with an understandable cost, while retaining the connected workflow Suite requires.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.