1C-Bitrix Database Optimization: Audit and Tuning

Your Bitrix site started slowing down: catalog pages loading in 5–7 seconds, admin panel freezes, operators complain about sluggish performance. The first thing to check is the database. Typical picture: cache tables have grown to gigabytes, sessions haven't been cleaned for years, indexes are fragmented, MySQL chokes on useless queries. We conducted a database audit for a large electronics e-store with 50,000 products and a load of 10,000 visitors per day. After cleanup and configuration tuning, page generation time dropped from 4.3 s to 1.1 s — result: a 12% conversion increase. Server resource savings reached 70% on CPU and memory. This 4x acceleration is achievable for every Bitrix site and pays off within a month.

Why aren't cache tables cleaned automatically?

In Bitrix, the caching mechanism leaves tags in b_cache_tag but does not delete them on cache reset. Similarly with sessions — b_user_session stores records until an explicit DELETE. Over a year, these tables can accumulate hundreds of megabytes of junk. For diagnosis, run the SQL query:

SELECT TABLE_NAME, ROUND((DATA_LENGTH + INDEX_LENGTH) / 1024 / 1024, 2) AS size_mb, TABLE_ROWS FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'bitrix_db' ORDER BY (DATA_LENGTH + INDEX_LENGTH) DESC LIMIT 20;

Typical "heavyweights": b_event_log, b_stat_session, b_cache_tag, b_search_content, b_file. Cleaning them is the first step to acceleration.

How to perform initial diagnosis yourself?

1. Connect to the DB via phpMyAdmin or console.
2. Run the query above — identify which tables take the most space.
3. Enable slow query log in MySQL and analyze slow queries over a day.
4. Check the size of /var/lib/mysql/ibdata1 — if it exceeds 10 GB while total data is under 2 GB, that's a signal for optimization.
5. Use SHOW PROCESSLIST to identify long-running queries in real time.

Speeding up slow queries through indexes

Enable slow query log and analyze queries without indexes. For Bitrix, common issues are missing indexes in b_iblock_element and b_sale_order. Add them:

CREATE INDEX ix_active_iblock ON b_iblock_element (ACTIVE, IBLOCK_ID, TIMESTAMP_X);
CREATE INDEX ix_user_status ON b_sale_order (USER_ID, STATUS_ID);

After index creation, query performance increases 3–5 times. For a catalog with 20,000 items, filtering by activity time drops from 2.1 s to 0.4 s.

Cleaning cache and session tables

Delete outdated cache tags and sessions:

DELETE FROM b_cache_tag WHERE SITE_ID IS NULL AND CACHE_SALT IS NULL;
OPTIMIZE TABLE b_cache_tag;

DELETE FROM b_user_session WHERE DATE_CREATE < DATE_SUB(NOW(), INTERVAL 24 HOUR);
DELETE FROM b_sale_user_session WHERE DATE_INSERT < DATE_SUB(NOW(), INTERVAL 7 DAY);

Regular cleaning of these tables reduces their size from gigabytes to megabytes and lowers MySQL load.

MySQL configuration for maximum performance

The most important parameter is innodb_buffer_pool_size. For a server with 8 GB RAM, set:

innodb_buffer_pool_size = 4G
innodb_log_file_size = 512M
innodb_flush_log_at_trx_commit = 2

innodb_flush_log_at_trx_commit = 2 gives a write performance boost of 2–5 times with minimal reliability loss. According to Wikipedia, this parameter is critical for InnoDB performance. Additionally set query_cache_type = 0 — in modern MySQL versions it is deprecated and only slows things down.

Before and after optimization comparison

What's included in the work

• Diagnosis of all tables and slow query log.
• Cleanup of cache, sessions, event log.
• Optimization of indexes and fragmented tables.
• my.cnf tuning according to load.
• Maintenance schedule (SQL scripts via cron).
• Consultation and support within a month after work.

We are a team of certified Bitrix specialists with over 7 years of experience. We have conducted 50+ audits and guarantee at least a 2x speed improvement. Order a consultation — we will assess your database's current state for free. Contact us to receive a detailed report with recommendations.

Work timeline

Server resource savings — up to 70% load on the database. For more on methodologies, read on Wikipedia.

What if the site stops working after DB optimization?

If after our work the site becomes unresponsive, possible causes are an incorrect MySQL parameter or an erroneous DELETE. We always create a backup before making changes. If you performed the optimization yourself, restore the dump and contact us for help.

Typical mistakes in self-optimization

The most common mistake is a DELETE without WHERE or with the wrong condition. This can destroy critical data. The second risk is changing MySQL parameters without understanding the consequences: for example, innodb_flush_log_at_trx_commit = 1 (safe but slow) versus = 2 (fast but possible loss of 1 second of data on crash). We always create a backup before any changes. If in doubt — entrust the audit to professionals. Contact us for a free initial diagnosis.

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.