pattern-flyweight

To reduce memory usage for thousands of similar objects, you separate intrinsic shared state from extrinsic contextual state and use a factory-managed pool to reuse shared instances instead of duplicating data. This prevents high memory consumption during large-scale rendering workloads.

The flyweight pattern is a structural design pattern that minimizes memory by sharing intrinsic immutable state across many object instances. A central factory manages a pool of these shared objects, handing out existing instances to clients rather than creating duplicates.

Use a factory-managed pool for high-volume object collections when rendering fleets of entities or caching reference data, such as drawing thousands of trees or caching configuration for large numbers of availability slots. It stops the system from becoming inefficient by wasting memory.

To optimize memory in TypeScript, categorize object fields into intrinsic shared immutable attributes and extrinsic contextual data. Clients supply their unique extrinsic coordinates or schedules, while the factory holds and reuses the single copy of intrinsic shared attributes across all records.

A limitation of using shared state for memory optimization is the strict requirement to separate intrinsic and extrinsic state, forcing clients to manage all unique contextual data externally. If objects cannot be cleanly divided into shared and contextual fields, the structural pattern will not reduce memory effectively.