orchardcore-caching

To configure distributed caching in Orchard Core, integrate IDistributedCache to enable cross-instance cache sharing via Redis. This allows multiple application instances to share cached data, improving scalability across distributed deployments.

Cache invalidation in Orchard Core uses ISignal and CacheContext to trigger cache refreshes when content changes. This mechanism ensures dynamic shape caching remains fresh by invalidating specific cached fragments upon content updates.

The best way to enable response compression is by activating the OrchardCore.ResponseCompression feature. This reduces payload sizes and improves page load times across Orchard Core modules without modifying individual controller logic.

Yes, OrchardCore.DynamicCache supports fragment caching directly within Razor and Liquid templates. It allows you to cache specific rendered shapes or partial views, significantly improving page load times for dynamic content.

You need Orchard Core caching when dynamic content causes repetitive rendering overhead. Configuring dynamic shape caching and response compression optimizes performance by storing rendered fragments and reducing processing for repeated requests.

Cache invalidation issues often occur when ISignal triggers are not properly configured within the CacheContext. Ensure signals are fired on content changes so the corresponding cached fragments are explicitly invalidated and refreshed.