Ren'Py Persistent Object Size Limit Configuration for Low-Traffic Workloads

Goal: Minimize the disk footprint of Ren'Py save games for a low‑traffic visual novel by controlling how much data is stored in the persistent object across playthroughs.

Constraint: The engine documentation does not expose a direct setting to cap the size of persistent data or to automatically prune old entries, yet the cautions note that uncontrolled growth can increase load times and bloat save files.

Uncertainty: It is unclear whether developers can enforce a maximum size, enable compression, or trigger selective cleanup of persistent variables without modifying the core engine.

Questions: Is there a configuration option or runtime call to limit the persistent object’s size? Can persistent data be segmented or expired based on playthrough count? Does Ren'Py provide a hook to compress or serialize persistent data more efficiently?