Cache Mode
Large Stimulsoft reports can consume memory both while PPJ prepares data and while the engine renders pages. There is no fixed safe page count: images, layout complexity, process architecture, and concurrent reports all matter.
Report Page Cache
The historical Reports.NET integration exposes Report Cache Mode:
| Mode | Behavior |
|---|---|
| Off | Keeps rendered pages in memory without the report's disk page cache. |
| On | Enables page caching from the start of rendering. |
| Auto | Starts caching after the configured threshold. |
Engine versions exposing StiOptions.Engine.ReportCache can configure LimitForStartUsingCache, AmountOfQuickAccessPages, and CachePath. Verify these properties against the installed engine. This page cache is distinct from a web viewer's session/report cache.
Configuration and Measurement
Set shared engine options during initialization; changing static settings during concurrent reports can affect other work. Use a writable cache directory with sufficient free space and an appropriate cleanup policy. Cached report pages can contain the same business data as the final output.
Measure peak memory separately during data preparation, rendering, and export. Page caching does not remove the memory required for PPJ's source DataSet. Consider reducing the input, splitting an output, or using a supported 64-bit deployment when those fit the workflow. Test the entire dependency chain before changing architecture.
Consult the Stimulsoft documentation matching the installed Reports.NET version for cache behavior and defaults.