1C-Bitrix Sharding: Master-Slave, Module Separation & Cache Tuning

Optimizing 1C-Bitrix Performance with Database Sharding

Partitioning splits a table within one server. Sharding distributes data across multiple database servers. When a single MySQL server cannot handle the load (100% CPU, disk I/O bottleneck), horizontal scaling via sharding is an option. For Bitrix, this is a non-trivial task because the core is designed to work with one database. According to the Bitrix Cluster Module Documentation, the built-in cluster module supports master-slave and module-level separation but not full sharding. Our team, with 7+ years of Bitrix experience, has completed over 100 high-load projects. We have 30+ certified specialists and a 98% client satisfaction rate.

When Is Sharding Needed?

If after configuring caching (Redis, tagged cache), enabling composite mode, and setting up master-slave replication the database still hits CPU limits, it's time to consider sharding. On one project with a catalog of 2 million products, complex queries took 30 seconds without sharding. After offloading the statistics and search modules to separate servers, the time dropped to 300 ms — a 99% improvement for those queries. In another case, we reduced database CPU usage from 95% to 40% within a week.

Built-in Mechanism: the cluster Module

Bitrix provides the cluster module (available in Business and Enterprise editions). It supports:

• Master-slave replication — writes to master, reads from one or more slaves. Not pure sharding, but relieves read load.
• Moving modules to a separate database — a specific module (e.g., search or statistic) can use its own database on another server.

Configuring master-slave via cluster:

1. Set up MySQL/MariaDB replication using standard methods (GTID or positional).
2. In the Bitrix admin panel: Settings → Web Cluster → Databases → Add.
3. Provide the slave server parameters: host, port, login, password.
4. Bitrix automatically routes SELECT queries to the slave, and INSERT/UPDATE/DELETE to the master.

The module monitors replication lag (Seconds_Behind_Master) and switches reads back to the master if the threshold is exceeded.

Module-Level Sharding

The cluster module allows moving tables of a specific module to a separate database server. In practice:

• statistic module — tables b_stat_* generate 80% of INSERT load on a typical site. Moving them offloads the main database.
• search module — tables b_search_* are heavy for full-text search. An alternative is to offload search to Elasticsearch.
• forum / blog module — if the forum or blog is active, their tables can be isolated.

Configuration: Web Cluster → Databases → [server] → Modules — select the module to move. Bitrix redirects queries to that module's tables to the specified server.

Horizontal Data Sharding

Full sharding — splitting one table by a key (e.g., products with IDs 1–100000 on server A, 100001–200000 on server B) — is not supported out of the box by Bitrix. The D7 ORM and the legacy API work with a single database connection.

Implementation is possible but requires:

• A proxy layer — Vitess or ProxySQL routes queries according to sharding rules transparently to the application.
• A custom DB class — inheriting from Bitrix\Main\DB\MysqliConnection with routing logic.
• Limitations: JOINs across shards are impossible, aggregate queries must be collected in the application.

In practice, full horizontal sharding for Bitrix is rarely used. More common is a combination: master-slave + offloading heavy modules + caching.

Impact of Sharding on Architecture

Sharding requires changing query logic: JOINs only within a shard, aggregates via UNION, transaction support only at the shard level. If sharding is implemented via a proxy layer, the application does not change, but the proxy handles routing and can become a bottleneck. Our experience: Vitess is better than ProxySQL for Bitrix because it supports automatic shard rebalancing.

Process of Setup

1. Audit the current database architecture, measure load, analyze slow query logs.
2. Choose a topology: master-slave, module offloading, or sharding.
3. Configure replication and monitoring (lag < 1 sec).
4. Move modules to separate servers, conduct load testing.
5. If full sharding is needed, install a proxy, migrate data.
6. Optimize caching: Redis, tagged cache, composite mode.

Timelines — from 2 weeks for master-slave to 2 months for full sharding. Typical cost ranges from $5,000 to $20,000 depending on complexity. Clients typically save 30-50% compared to upgrading all hardware.

What's Included in the Work

We provide:

• Architecture diagram with data location.
• Configuration files for MySQL/MariaDB, ProxySQL/Vitess.
• Scripts for monitoring lag and integrity.
• Documentation for disaster recovery procedures.
• Training for administrators and developers.
• Guarantee of stable operation — 30 days of 24/7 support after launch.

Contact us for an assessment of your project. Our team: 7+ years of Bitrix experience, 100+ high-load projects, 30+ certified specialists, 98% client satisfaction rate. Get a consultation on sharding — reach out, and we'll estimate the scope of work.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.