Configuring Autocaching of 1C-Bitrix Components: 2-5x Speedup

We encounter projects where, after major updates or development by third-party teams, pages load in 5–10 seconds. A typical cause is incorrect autocaching parameters of components. Configuring autocaching of 1C-Bitrix components can drastically reduce response time. Let's dive into how it works and how to configure it. For example, on one project with a catalog of 10,000 items, pages took 7 seconds to load. After configuring autocaching, TTFB dropped to 0.2 seconds, leading to substantial server resource savings. Proper autocaching makes the site 2-5 times faster compared to an unoptimized one.

Autocaching as the Foundation of Bitrix Performance

Autocaching in Bitrix is a built-in mechanism of the component system where the component's output (HTML or data) is saved to file cache and reused on subsequent requests. In a properly configured project, 70–90% of component calls are served from cache without database queries. Without it, each request burdens the database, which is critical under high load.

How the Cache Key is Formed and Why It Matters

Bitrix forms the cache key from component parameters, URL, and additional variables. The problem arises when extraneous data enters the key: session ID, random GET parameters like UTM tags (utm_source, utm_campaign), pagination parameters.

A component with CACHE_FILTER = Y will create a separate cache for each combination of GET parameters — under UTM traffic, the cache will never be reused. Solution: set CACHE_FILTER = N and explicitly pass only significant parameters via arAdditionalCacheId, or filter UTM parameters at the nginx level before passing the request to PHP.

Why CACHE_GROUPS = Y Can Be a Problem

The CACHE_GROUPS = Y parameter creates a separate cache for each user group. This is needed for components with content that depends on permissions. But for a public catalog or news, CACHE_GROUPS = Y multiplies the number of cache entries by the number of user groups. On projects with 20+ groups (partners, wholesalers, managers, etc.), the cache never "warms up" to the point of being effectively used. Order an audit — we will identify and eliminate such issues.

Comparison of Caching Modes

Case Study from Our Practice

A manufacturing company's Bitrix "Standard" site. The client complained: the site was fast, but after a template update everything became slow. We conducted an audit using the performance panel — all components were running without cache. The cause: the developer, for ease of debugging, set the constant BX_CACHE_TYPE to N in bitrix/php_interface/dbconn.php and forgot to remove it. One line of code — and the entire site ran without caching. Fixing it took 15 minutes, TTFB returned to normal. Such situations are not uncommon, and our inspection of dozens of projects shows that in 80% of cases the problem is solved by simple constant configuration. This data is derived from audits of over 500 projects.

How We Configure Autocaching: The Process

Our team has 10+ years of Bitrix experience and over 500 successful projects. Recommendations are based on more than 10 years of working with Bitrix. The process includes stages:

1. Audit — collect metrics, analyze components via the performance panel.
2. Design — determine TTL for each block, configure keys.
3. Implementation — edit component calls, add tagged cache.
4. Testing — compare response times before/after (e.g., from 7 seconds to 0.2).
5. Deployment — move to production server, monitor.

We guarantee at least a 2–3x page load speedup. Server resource savings can be substantial on high-load projects. The experience of certified specialists allows us to identify even hidden issues.

What's Included in Turnkey Autocaching Configuration?

• Full revision of all component calls on the site.
• Correction of incorrect caching parameters.
• Configuration of tagged cache for custom components.
• Optimization of cache keys by removing extraneous parameters.
• Documentation of changes and maintenance recommendations.

Timeline: from 1 to 3 days depending on project size. Cost is calculated individually based on scope. Get a consultation on autocaching configuration — contact us.

Recommended TTL for Typical Components

Typical mistakes in cache configuration:

• Using CACHE_GROUPS = Y for public content.
• Incorrect cache keys with UTM parameters.
• Lack of invalidation for custom components.

Cache Invalidation

Component cache is automatically invalidated when the data of the information block it is tied to changes, via tags like IBLOCK_N_ELEMENTS. For custom components working with their own tables, invalidation must be explicitly implemented using BXClearCache() or \Bitrix\Main\Application::getInstance()->getTaggedCache()->clearByTag().

More details can be found in the official 1C-Bitrix documentation or on Wikipedia.

Configuring autocaching is a revision of all component parameters on the site, identifying incorrect cache keys, and setting proper TTLs. If you want to speed up your project, order an audit — we will diagnose and fix the issues.

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.