Memcached Setup for 1C-Bitrix: Caching, Sessions, Composite

A Bitrix site with 20,000 products starts slowing down during catalog filtering — page generation takes 5–7 seconds, and the database struggles with queries. The first thing we do in such projects is replace file-based cache with Memcached. This gives a 5–10x speed boost on catalog pages and reduces database load by up to 90%. In this article, we explain how to configure Memcached correctly to avoid issues with invalidation and data eviction.

Why Memcached Is Critical for High-Load Sites

Bitrix has built-in support for Memcached via the caching module. When properly configured, component cache, HTML pages (composite site), and sessions are stored in memory, bypassing the file system. On a server with HDD, Memcached is 5–10x faster than file cache. Memcached uses consistent hashing to distribute keys across nodes — this guarantees minimal redistribution when adding or removing a server.

Typical Pain Points That Memcached Solves

• Slow catalog page loads due to reading cache from disk
• Increased database load during peak traffic (up to 5000 rps)
• Cache loss after web server restart (file cache does not persist)
• Inefficient memory usage: file cache consumes disk space instead of RAM

How We Set Up Memcached Turnkey

Our engineers have 10+ years of experience with Bitrix and have completed over 100 optimization projects. We use only current versions: PHP 8.1+, Memcached 1.6+, php-memcached extension. We guarantee stability and performance gains. Typical cost: $500–$1500 depending on complexity, but the investment recoups within 2–3 months through reduced server expenses.

Our Process

1. Analysis — measure current performance, identify bottlenecks (up to 2 hours)
2. Design — calculate memory size, connection count, kernel parameters
3. Installation and Configuration — set up Memcached, connect to Bitrix via .settings.php
4. Testing — check hit rate, invalidation, compatibility with composite mode
5. Optimization — configure TTL, tagged caching, monitor evictions
6. Documentation — hand over configs and maintenance instructions

Timeline: 1 to 3 business days depending on project architecture. Cost is determined after analysis; typically recouped within 2–3 months through reduced server load.

What's Included

• Memcached configuration files with optimal parameters
• Connection setup to Bitrix (.settings.php, php.ini for sessions)
• Enable tagged caching and configure cache_flags.php
• Monitoring scripts for statistics (hit rate, evictions)
• Documentation: configuration description and maintenance guide
• Training: cache management consultation for your administrator
• Support: 2 weeks after setup to resolve any issues

How to Avoid Evictions

Evictions occur when Memcached removes old data to make room for new data. If evictions grow continuously, you need more memory. In Bitrix, this often happens when caching large HTML blocks (e.g., catalog sections). The solution is to increase the -m parameter in the configuration. For a project with 10,000 products and 500 daily visitors, 2 GB is usually sufficient.

How to Connect Memcached to Bitrix

Installation and basic configuration:

apt install memcached php-memcached

# Configuration /etc/memcached.conf
-d                        # daemon mode
-m 1024                   # memory in MB
-u memcache
-l 127.0.0.1              # localhost only
-p 11211
-c 1024                   # max connections
-I 32m                    # max item size (for large cache objects)
-t 4                      # threads (= number of cores)

The -I 32m parameter is critical: the default limit is 1 MB, but a catalog page with 50 products may generate HTML of 2–5 MB. Without increasing it, the cache silently fails to store large objects.

Connecting to Bitrix:

<?php
// /bitrix/.settings.php
return [
    'cache' => [
        'value' => [
            'type' => 'memcache',
            'memcache' => [
                'host' => '127.0.0.1',
                'port' => '11211',
            ],
            'sid' => 'bitrix_cache',
        ],
    ],
];
?>

; php.ini for session cache
session.save_handler = memcached
session.save_path = "127.0.0.1:11211"

Alternatively, use the admin panel: Settings → Product Settings → Cache and select "Memcache".

How to Check Cache Efficiency

# Basic statistics
echo "stats" | nc 127.0.0.1 11211 | grep -E "curr_items|bytes|get_hits|get_misses|evictions"

# Calculate hit rate
hits=$(echo "stats" | nc 127.0.0.1 11211 | grep get_hits | awk '{print $3}')
misses=$(echo "stats" | nc 127.0.0.1 11211 | grep get_misses | awk '{print $3}')
echo "Hit rate: $(echo "scale=2; $hits / ($hits + $misses) * 100" | bc)%"

Hit rate is the key metric. If below 80%, the cache is inefficient: either TTL is too short or objects are evicted prematurely. Monitor evictions — if they increase, increase -m.

Memcached vs Redis for Bitrix

For component cache and HTML, Memcached is sufficient. For task queues, counters, pub/sub, use Redis.

Common Configuration Mistakes

Typical Problem: Stale Cache After Updates

Bitrix invalidates cache by tags. When a product is updated, all caches containing that product's tag are invalidated. If invalidation doesn't work, check that the tag system is correctly configured in cache_flags.php:

<?php
// bitrix/php_interface/cache_flags.php
$GLOBALS['CACHE_FLAGS'] = [
    'iblock_id_list' => true,
    'catalog_price' => true,
];
?>

Also ensure that components have not disabled tagged caching in their settings. After proper setup, you reduce server hardware costs and accelerate project ROI.

Additional Resources

For more on Memcached, see Wikipedia. For Bitrix-specific setup, refer to the 1C-Bitrix documentation.

Contact us for a free consultation and project analysis. Order our turnkey Memcached setup and get a speed boost in 1–3 days.

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.