bitrix-caching

Reduce Bitrix database queries by wrapping critical components with startResultCache and endResultCache to enable component caching. This prevents redundant data fetching on repeated requests and significantly lowers rendering overhead.

ManagedCache in Bitrix provides time-bounded caching for standard results, while TaggedCache enables group-based invalidation. Tagged cache allows you to clear cached data across multiple components simultaneously when underlying data changes via specific tags.

Configure memcached or redis cache engines in the .settings.php file. Defining the cache engine configuration here allows Bitrix to route caching operations to your preferred high-performance storage instead of default file-based caching.

Yes, you can cache Bitrix ORM query results by setting the isCacheable method to true and configuring getList cache options. This allows the ORM to store query outputs and serve them directly on subsequent identical requests.

The best way to invalidate Bitrix cache is using tag-based invalidation strategies via events. By assigning tags to cached data, changes in underlying records trigger events that automatically clear only the affected cache entries.

Use Bitrix composite cache for full-page performance when you need to cache entire page outputs, and use component caching for individual data blocks. Composite cache requires careful integration but supports cache warm-up for high traffic.