Bitrix Managed Cache Setup: Redis & Tagged Caching

Bitrix Managed Cache Setup: Redis & Tagged Caching

Imagine an online store with a catalog of 50,000 items. Every hour prices update from 1C — and the entire cache is cleared. The server goes down under load, pages load in 10 seconds. Sound familiar? Managed cache (Механизм тегированного кеширования) solves this without capital investment. We set it up turnkey on Redis or memcached — with guaranteed results. Our experience: over 10 years and 50 successful Bitrix projects. You get savings in server resources and several-fold site acceleration without increasing your hosting budget.

How Managed Cache Solves Performance Problems

Managed cache (\Bitrix\Main\Data\ManagedCache) works on a tag principle: each cached object is marked with a unique identifier. When data updates, only that tag is cleared, not the entire infoblock. This yields 5–10x speed improvement on pages unaffected by changes.

Example from our practice: an online store with hourly 1C exchange (500–2000 items) — after implementing granular iblock_element_ID tags, page load time dropped from 8 seconds to 0.4. Cache was cleared only for changed items, not the whole catalog.

What is Tagged Caching and How It Works

Tagged caching is an approach where each cached data fragment is associated with one or more tags. Tags are string identifiers, e.g., iblock_id_5 or element_123. When changes occur (price update, product addition), you invalidate only the corresponding tag, not the entire cache. This minimizes cache regeneration and reduces server load.

How Managed Cache Is Structured

The class \Bitrix\Main\Data\ManagedCache works atop a storage backend — by default memcached or Redis (configured in /bitrix/.settings.php). Tags are stored separately from data: each tag is a version counter. When a tag is invalidated, the counter increments; all records with an outdated tag version are considered invalid.

Example usage in a component:

$managedCache = Application::getInstance()->getManagedCache();
$cacheTag = 'iblock_id_' . $ibId;

if ($managedCache->read(3600, 'my_cache_key', $cacheTag)) {
    $result = $managedCache->get('my_cache_key');
} else {
    $result = /* heavy query */;
    $managedCache->set('my_cache_key', $result);
    $managedCache->registerTag($cacheTag);
}

Calling \Bitrix\Main\TaggedCache::clearByTag('iblock_id_5') clears only data marked with that tag — other components keep working from cache.

Configuring Redis as Backend

For production Redis is recommended — it's faster than memcached when working with tags and supports persistence. Configuration in /bitrix/.settings.php:

'cache' => [
    'value' => [
        'type' => [
            'class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis',
            'extension' => 'redis',
        ],
        'sid' => 'mysite',
        'host' => '127.0.0.1',
        'port' => 6379,
        'serializer' => Redis::SERIALIZER_IGBINARY,
    ],
],

Parameter serializer => IGBINARY is important: it reduces the size of serialized PHP objects by 30–50% compared to the default serialize().

Learn more about Redis in the official documentation and about tagged caching in Wikipedia.

Why Redis is Better Than Memcached for Managed Cache

Redis wins due to:

• Persistence — data is not lost on restart (if disk saving is enabled).
• Support for complex structures — tags can be conveniently stored as hashes or sets.
• Built-in igbinary — reduces data size by 30–50%.
• Faster tag invalidation thanks to atomic operations.

Benchmarks show that Redis read/write speed for tags is 2–3 times higher than memcached, especially with many tags (10,000+).

How We Set Up Managed Cache: Step-by-Step

1. Audit current state: check Bitrix version, presence of main module 20+, identify components not using ManagedCache.
2. Choose backend: if Redis is already on the server, use it. Otherwise, set up Redis or propose memcached.
3. Edit .settings.php: specify host, port, igbinary serializer.
4. Refactor components: replace getCache() with ManagedCache, add granular tags by item ID, section ID, infoblock ID.
5. Test: load testing, invalidation verification, metrics.
6. Document: provide the team with instructions for adding new components.

What's Included in Turnkey Managed Cache Setup

Timeline and Pricing

Setup takes 1 to 3 business days depending on the number of components and server readiness (Redis availability). Pricing is calculated individually after a free audit — just contact us and we'll send a detailed estimate.

How to Avoid Common Setup Mistakes

Carefully verify tag registration: every set call must be accompanied by registerTag. Ensure Redis is configured for persistence (save). Use tags not only for items but also for sections, properties, metadata. Load testing before deployment is mandatory — otherwise you risk cache invalidation at peak times.

Get a consultation — we'll help you with your project. Contact us for a free audit of your current cache.

80% of Bitrix sites slow down due to one table

b_iblock_element_property is an EAV structure where each row stores one value of one property of one element. A catalog of 50,000 products with 30 properties yields 1.5 million rows. The smart filter performs a JOIN of this table with b_iblock_element on five properties, and MySQL performs a full table scan for 3–5 seconds. Our experience shows that without intervention in this table, site acceleration is impossible. We take on projects where load time has dropped to 8–10 seconds and bring TTFB back to <200 ms within 1–2 weeks. Site speed optimization begins with an audit of slow queries and ends with a comprehensive turnkey infrastructure overhaul.

Contact us for an audit — we will identify bottlenecks within 2 hours and propose a concrete plan.

How to achieve TTFB below 200 ms?

Server optimization is the first step. Nginx configuration goes beyond simple gzip. Specifically:

• gzip_comp_level 4-5 — higher is pointless, CPU consumes more than it saves bandwidth.
• brotli on with brotli_static on for precompressed files.
• HTTP/2 with http2_max_concurrent_streams 128.
• fastcgi_cache for PHP responses — caching at Nginx level, bypassing PHP-FPM entirely.
• worker_processes auto, worker_connections according to the number of simultaneous connections.

PHP-FPM tuning: choose between pm = dynamic and pm = static. Static mode works best for dedicated servers with predictable load because it avoids forking overhead. Dynamic saves RAM under low traffic. Calculate pm.max_children as (available RAM - RAM for MySQL/Redis) / average process consumption. For OPcache set memory_consumption=256, max_accelerated_files=20000, and validate_timestamps=0 in production (restart PHP-FPM on deploy).

MySQL/MariaDB: the main bottleneck is almost always the database. Enable slow_query_log with a threshold of 0.5 sec and analyze every query via EXPLAIN. Set innodb_buffer_pool_size to 70–80% of available RAM on a dedicated server. Create composite indexes for faceted search: (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) on b_iblock_element_property. Run OPTIMIZE TABLE b_iblock_element_property after mass operations.

How to configure three-level caching?

Managed component cache. Set TTL individually for each component. Catalog — 3600 sec, news feed — 300 sec, banners — 86400. The same TTL everywhere guarantees either outdated data or useless cache.

Composite cache. The bitrix:composite technology lets Nginx serve ready HTML from a file; PHP is not executed. Dynamic zones (cart, authorization) are loaded via AJAX request through CBitrixComponent::setFrameMode(true). TTFB drops below 50 ms. However, not all components are compatible; $APPLICATION->ShowPanel() and direct output via echo break the composite. We check every page through the panel 'Performance → Composite Site'. According to Bitrix official documentation on composite cache, this is the most effective caching method for high‑load projects.

Comparison: composite cache is 10–20 times faster than managed cache in time to first byte.

Memcached / Redis. Transfer cache from the file system: sessions go to Redis (session.save_handler = redis) — 10–50 times faster than files, plus cluster support. Component cache goes to Memcached via .settings.php: 'cache' => ['type' => 'memcache']. Also enable ORM query cache so identical GetList() calls don't hit MySQL on every request.

What is the fastest way to optimize Bitrix database?

Default MySQL settings are insufficient. Indexes — composite for faceted search, covering for frequent queries. MySQL responds from the index without accessing the data. Partial indexes (MariaDB) for filtering by ACTIVE = 'Y'. Audit unused indexes — each slows down INSERT/UPDATE.

Partitioning. For tables with millions of rows: b_stat_session, b_search_content_stem, and highload-blocks with history. Partition by date — a query for 'orders in a month' does not scan three years of data. Partitioning also solves the problem of concurrent queries during exchange with 1С via CommerceML.

Real case: a catalog of 200,000 products, 50 properties. Filtering by 10 properties took 12 seconds. After creating composite indexes on (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) and partitioning b_iblock_element_property by IBLOCK_ID, execution time dropped to 0.3 seconds. MySQL load decreased by 40 times.

Cleanup. Over a year or two, any database accumulates: outdated search index, expired records in b_cache_tag, history in b_iblock_element_prop_s*, logs in b_event_log taking gigabytes. We set up regular cleanup via agents.

Frontend and CDN

Images account for 60–80% of page weight. Convert to WebP via CFile::ResizeImageGet() with BX_RESIZE_IMAGE_PROPORTIONAL + conversion. Use srcset + sizes — never load a 3000px image into a 400px block. Add loading="lazy" for everything below the fold. AVIF offers another 20–30% savings vs WebP.

CSS/JS optimization: use the built-in Bitrix module to merge and minify via 'Settings → CSS/JS Optimization'. Apply PurgeCSS / UnCSS — in a typical Bitrix project, 60–70% of CSS is unused. Use defer / async for non‑critical JS and inline critical CSS in <head> for instant FCP.

Fonts: add <link rel="preload" as="font" crossorigin> for the main font. Set font-display: swap — text visible immediately. Subset via pyftsubset — keep only Cyrillic + Latin, file size reduces by 3–5 times.

CDN: Cloudflare, BunnyCDN, AWS CloudFront, or Russian providers (Selectel CDN, VK Cloud CDN). Serve static assets (CSS, JS, images, fonts) via CDN with Cache-Control: public, max-age=31536000, immutable for files with a hash. Use on‑the‑fly image optimization (imgproxy, Cloudflare Polish) without load on origin.

Why is load testing necessary?

Not synthetic benchmarks, but real scenarios: k6 / wrk to simulate routes — catalog → filtering → product card → cart → checkout. Measure RPS, response time (p50, p95, p99), error rate. Use Xdebug (callgrind) or Blackfire for PHP profiling to find bottlenecks. The test result gives an objective picture of where it actually slows down, not where it 'seems'. After optimization, run again to record improvements.

Results

What is included in the work?

1. Current performance audit — analysis of slow queries, PHP profiling, check of caching, CDN, server settings.
2. Server configuration — Nginx, PHP-FPM, MySQL, Redis/Memcached, OPcache.
3. Caching optimization — managed cache, composite site, TTL configuration, tagged caching.
4. Database work — index creation, partitioning, cleanup, EAV table reorganization.
5. Frontend — images (WebP/AVIF), CSS/JS (minification, deferred), fonts (preload, subsetting).
6. CDN — connection, caching rule setup.
7. Load testing — real user scenarios, metric report.
8. Documentation — description of all changes, recommendations for further maintenance.
9. Guarantee — support for 1 month after delivery, ensuring all optimizations are stable.

Monitoring

Without monitoring, everything degrades in six months. A new module, uncleared logs, a template change — and speed returns to original. Use web-vitals API for Real User Monitoring from actual visitors. Set up synthetic monitoring with Pingdom or UptimeRobot for regular checks from different locations. Configure alerts — TTFB > 500 ms or LCP > 3 sec triggers notification.

Timelines and cost

Cost is calculated individually after the audit. Get a consultation for your project — we will evaluate the current state and propose an acceleration plan with specific timelines and budget. We are a team with 12+ years of experience in Bitrix, having completed over 300 site speed optimization projects. Contact us to start the performance audit today.