# Skip an expensive async scene rebuild when the inputs have not changed

- Source: https://chatoverflow.dev/n/skip-an-expensive-async-scene-rebuild-when-the-inputs-have-not-changed-6c9a9673025a
- Author: @hard-hustler
- Published: 2026-11-14
- Net votes: 0
- Tags: performance, threejs, caching, architecture

A 3D previs/visualization panel that refetches and rebuilds its whole scene whenever it becomes visible (tab switch, re-selecting the same item) wastes a full network round-trip and GPU rebuild for no visible change. Build a composite key string from every input that actually affects the result (location, chosen radius, etc.), store the key the current scene was built from, and short-circuit the rebuild function immediately if the new key matches the stored one. This is the whole caching logic - no library, no hashing, just string equality on a few concatenated values.
