Elasticsearch Index Optimization for 1C-Bitrix

Picture this: a catalog of 100,000 products, nightly sync with 1C, and after it, Elasticsearch heap utilisation spikes to 85%. Search queries take 3–5 seconds, and merge throttling during indexing eats CPU. Sound familiar? Default ES settings are fine for small volumes, but for Bitrix stores with tens of thousands of items, they are completely unsuitable. Our team of certified Elasticsearch engineers has 10+ years of experience with Bitrix and Elasticsearch, and we have optimized over 50 catalogs. Our optimization service starts at $1,200 and typically saves clients $300-500 monthly on server costs. We share proven methods guaranteed to improve performance.

Optimizing Elasticsearch indices for 1C-Bitrix delivers measurable results. After tuning, search latency drops to 50–150 ms (20x faster than default settings), heap utilisation decreases by 30–50%, and nightly reindexing speeds up 3–5 times. Below are typical metrics before and after.

The comparison is clear: 20x difference in latency and 3x in indexing. This gives users consistently fast search and reduces server load. Our optimized configuration is 20 times faster than default settings for search queries and 3 times faster for indexing.

How to Speed Up Bitrix Search with Elasticsearch?

Why Default ES Configuration Is Inefficient?

Bitrix generates a specific load: frequent bulk reindexing (sync with 1C), huge number of text fields for search, faceted filters on dozens of attributes. Out of the box, ES allocates 3–5 shards per catalog—too few for 200 GB of data, and fielddata on text fields eats heap. The result is degradation that only worsens over time. For elasticsearch optimization bitrix, proper elasticsearch tuning 1c bitrix involves adjusting sharding and merge policy. Bitrix search performance relies on elasticsearch indices bitrix configuration. Elasticsearch sharding and merge policy are key.

# Cluster health
GET /_cluster/health?pretty

# Index statistics
GET /bitrix_catalog/_stats?pretty

# Hot threads (what's loading CPU)
GET /_nodes/hot_threads

# Memory usage
GET /_nodes/stats/jvm?pretty

Step-by-Step Index Configuration

Follow these steps to optimize your Elasticsearch indices for Bitrix.

Step 1: Sharding Configuration

The most common mistake is too many shards. Each shard is a Lucene index with ~50 MB heap overhead. 100 shards = 5 GB heap just for metadata.

For a Bitrix catalog rule: 1 shard per 20–40 GB of data, no more than 3–5 shards for a typical store:

PUT /bitrix_catalog
{
    "settings": {
        "number_of_shards": 3,
        "number_of_replicas": 1
    }
}

You cannot change the number of primary shards after index creation—you must create a new index and reindex via Reindex API. Plan correctly from the start.

Step 2: Optimizing Refresh Interval and Merge Policy

By default, ES refreshes the index every second—new documents become searchable within 1 s. This is costly during bulk indexing. During 1C sync (bulk indexing), we disable refresh, then restore it and trigger a manual refresh after completion.

Merge policy is tuned to disk type: for HDD limit to one thread, for NVMe two to four. Typical parameters:

PUT /bitrix_catalog/_settings
{
    "index.merge.policy.max_merged_segment": "5gb",
    "index.merge.policy.segments_per_tier": 10,
    "index.merge.scheduler.max_thread_count": 1
}

Step 3: Optimizing Fielddata and Doc Values

Fielddata is loaded into heap during aggregations and sorting on text fields. For catalog faceted filters, use exclusively keyword with doc values (stored on disk, not in heap):

PUT /bitrix_catalog/_mapping
{
    "properties": {
        "brand": {
            "type": "keyword",
            "doc_values": true,
            "eager_global_ordinals": true
        }
    }
}

eager_global_ordinals: true for high-cardinality filter fields (brand, category) builds ordinals at refresh time, not at first aggregation query. Eliminates "cold start" after nightly reindexing.

Step 4: Force Merge for Static Indices

If the catalog changes only nightly (1C sync once a day), merge the day-index into a single segment. This is a heavy operation, run only in a maintenance window. One segment = maximum search speed, minimal overhead.

Step 5: Configuring Indexing from Bitrix

On the PHP side, during bulk indexing use the Bulk API with an optimal batch size:

$batchSize = 500; // optimum for products with descriptions
$body = [];
foreach ($products as $product) {
    $body[] = ['index' => ['_index' => 'bitrix_catalog', '_id' => $product['ID']]];
    $body[] = $this->prepareDocument($product);
}
$client->bulk(['body' => $body]);

Batch size is tuned experimentally: too small means many round-trips, too large means GC pressure. Usually 200–500 documents for products with descriptions.

Monitoring After Optimization

Connect ES metrics to Prometheus via elasticsearch_exporter and alert on:

• heap_used_percent > 80% for more than 5 minutes
• GC time > 1 second per minute
• search latency p99 > 500 ms
• unassigned shards > 0

Results in Numbers: Before and After

Server resource savings reach 30–50%, directly reducing infrastructure costs.

What's Included in the Work

• Audit of current ES configuration and Bitrix infoblocks
• Calculation of optimal number of shards and replicas
• Mapping tuning for catalog specifics (keyword, doc_values, eager_global_ordinals)
• Merge policy and refresh_interval optimization for indexing mode
• Bitrix-side bulk-indexing tuning (batch size, tweaking)
• Monitoring integration (Prometheus + Grafana) and alerts
• Operations documentation

Contact us for a free audit of your cluster. We'll assess metrics and propose a turnkey optimization plan. Get a consultation—it takes no more than an hour. Request an audit now to see the difference in search speed. Our guaranteed results include documented improvements.

Learn more about Elasticsearch at Wikipedia and Lucene.

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.