Why a 128 MB Buffer Pool Slows Down Bitrix?
MySQL spends a whole second on a query that should run in 10 milliseconds. SHOW STATUS LIKE 'Innodb_buffer_pool_reads' returns tens of thousands of physical reads per minute — data is constantly read from disk. The cause is almost always the same: innodb_buffer_pool_size is set to the default 128 MB, while the working data set of a Bitrix site has long exceeded a gigabyte.
We have repeatedly encountered situations where owners of online stores on 1C-Bitrix complain about slowdowns under peak load, and the root of the problem is precisely the buffer pool. For example, recently on a project with 50,000 products, the hit_ratio was 87% — every seventh read went to disk. After tuning the pool to 4 GB, hit_ratio rose to 99.8%, average query time dropped from 350 to 20 ms. Over 5 years, we have tuned InnoDB on hundreds of projects and guarantee at least a 2-3x speedup in queries after proper configuration.
What is the InnoDB Buffer Pool and Why Its Size Is Critical
The buffer pool is the RAM allocated by InnoDB for caching data and index pages. If the working data set fits in the buffer pool, MySQL reads from RAM. If not, each miss costs several milliseconds of disk I/O. More about the mechanism can be read on Wikipedia.
A typical medium-sized Bitrix site:
-
b_iblock_element_property — 500 MB – 3 GB
-
b_iblock_element — 50–300 MB
-
b_catalog_price, b_catalog_product — 100–500 MB
- indexes for these tables — about the same
Total working set — 1–8 GB. The default 128 MB covers less than 10%.
Diagnosis and Calculation of Buffer Pool Size
How to Diagnose Insufficiency?
Run the queries:
SELECT (1 - (Innodb_buffer_pool_reads / Innodb_buffer_pool_read_requests)) * 100 AS hit_ratio
FROM (
SELECT VARIABLE_VALUE AS Innodb_buffer_pool_reads
FROM information_schema.GLOBAL_STATUS
WHERE VARIABLE_NAME = 'Innodb_buffer_pool_reads'
) r,
(
SELECT VARIABLE_VALUE AS Innodb_buffer_pool_read_requests
FROM information_schema.GLOBAL_STATUS
WHERE VARIABLE_NAME = 'Innodb_buffer_pool_read_requests'
) rr;
SHOW STATUS LIKE 'Innodb_buffer_pool_pages_flushed';
SHOW STATUS LIKE 'Innodb_buffer_pool_wait_free';
If hit_ratio is below 99% — the buffer pool is definitely too small. If Innodb_buffer_pool_wait_free is non-zero — critical shortage: write operations are waiting for free pages.
How to Calculate the Optimal Size?
Find the actual size of data and indexes:
SELECT
ROUND(SUM(data_length + index_length) / 1024 / 1024, 0) AS total_mb,
ROUND(SUM(data_length) / 1024 / 1024, 0) AS data_mb,
ROUND(SUM(index_length) / 1024 / 1024, 0) AS index_mb
FROM information_schema.TABLES
WHERE table_schema = 'your_database';
Rule: buffer pool = 70–80% of the working data set size, but not more than 70–80% of total server RAM. On a server with 8 GB RAM and a 4 GB database — set 4–5 GB.
Configuring Buffer Pool in my.cnf and Online Change
[mysqld]
innodb_buffer_pool_size = 4G
innodb_buffer_pool_instances = 4
innodb_buffer_pool_chunk_size = 128M
innodb_buffer_pool_instances — number of independent pools. Reduces thread contention for mutexes. Rule: 1 instance per 1 GB of pool, max 64. For a 4 GB pool — 4 instances.
innodb_buffer_pool_chunk_size must be a divisor of the total: innodb_buffer_pool_size = chunk_size * instances * N. In the example: 4G = 128M * 4 * 8 — correct.
MySQL 5.7.5+ supports online buffer pool resize:
SET GLOBAL innodb_buffer_pool_size = 4294967296; -- 4 GB in bytes
The resize process is asynchronous. Monitor progress:
SHOW STATUS LIKE 'Innodb_buffer_pool_resize_status';
While resizing, there may be a temporary performance drop. Change during a low-load window.
Which InnoDB Parameters Are Critical for Bitrix?
Besides buffer pool, it's important to set:
innodb_log_file_size = 512M
innodb_log_buffer_size = 64M
innodb_flush_method = O_DIRECT
innodb_io_capacity = 2000
innodb_io_capacity_max = 4000
innodb_flush_method = O_DIRECT is critical on Linux: without it, data is cached twice — in the InnoDB buffer pool and in the kernel page cache. This wastes RAM.
Monitoring and Results
Monitoring After Changes
After 30–60 minutes under load:
SELECT ROUND(Innodb_buffer_pool_bytes_data / 1024 / 1024 / 1024, 2) AS cached_gb
FROM (SELECT VARIABLE_VALUE AS Innodb_buffer_pool_bytes_data
FROM information_schema.GLOBAL_STATUS
WHERE VARIABLE_NAME = 'Innodb_buffer_pool_bytes_data') t;
SELECT ROUND(
(SELECT VARIABLE_VALUE FROM information_schema.GLOBAL_STATUS
WHERE VARIABLE_NAME = 'Innodb_buffer_pool_pages_data') /
(SELECT VARIABLE_VALUE FROM information_schema.GLOBAL_STATUS
WHERE VARIABLE_NAME = 'Innodb_buffer_pool_pages_total') * 100, 1
) AS pool_used_pct;
If pool_used_pct is consistently 95–100% — the pool is full; consider increasing. If 60–70% — current size has headroom.
Performance Comparison Before and After Tuning
| Parameter |
Before (128 MB) |
After (4 GB) |
| Hit ratio |
85–92% |
99.5%+ |
| Avg query time |
450 ms |
25 ms |
| Innodb_buffer_pool_reads/sec |
15,000 |
50 |
| Disk load (iowait) |
30% |
2% |
| Project Type |
Recommended RAM |
Recommended Buffer Pool |
| Store up to 10,000 products |
4 GB |
2 GB |
| Store up to 50,000 products |
8 GB |
5 GB |
| Store up to 200,000 products |
16 GB |
10 GB |
Typical Mistakes in Configuration
- Setting size larger than available RAM (causes swap).
- Ignoring
innodb_flush_method = O_DIRECT on Linux.
- Changing size online without monitoring progress.
- Choosing values not multiples of
chunk_size (rounding error).
What's Included in a Turnkey Buffer Pool Tuning
- Diagnosis of current state: hit_ratio, data size, configuration.
- Calculation of optimal size considering RAM and load.
- Parameter changes (buffer pool, log, flush method) with online application.
- Post-change monitoring and report with recommendations.
- Consultation on other bottlenecks (indexes, Bitrix caching).
- Guarantee on result: hit_ratio > 99% after pool warm-up.
Contact us for a free preliminary diagnosis. Order buffer pool tuning and get database acceleration today. We'll help select the configuration for your project and ensure stable performance under peak load.
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.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
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?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.
