Boost Your Bitrix Site with Varnish Caching
Imagine a catalog with 50,000 items: each PHP request generates a page in 300–800 ms. With 50 concurrent visitors, the server hits CPU and memory limits, and response time grows to 3–5 seconds. Varnish is a reverse-proxy cache at the Linux kernel level that stores response copies in RAM and serves them in 1–5 ms without involving PHP. Proper Varnish Bitrix caching configuration yields 10x speed improvement. With over 10 years in web performance and 5 years specializing in Bitrix caching, we have completed 200+ projects. Our team holds Bitrix certifications. We configure Varnish for Bitrix considering all specifics: sessions, cart, authorization, Composite. Our experience — over 7 years working with Bitrix, dozens of caching projects.
"Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy." — Wikipedia
How Varnish Solves Bitrix Performance Problems
For anonymous visitors, Varnish turns a dynamic PHP site into a static one, reducing load time from seconds to milliseconds. However, Bitrix assigns a session cookie PHPSESSID even to anonymous users with an empty cart. The standard Varnish policy — not caching requests with Set-Cookie — disables caching for everyone. Our VCL configuration carefully removes service cookies (analytics, ads) and allows caching if no critical cookies remain. Varnish is 5 times faster than Nginx FastCGI Cache for static delivery: under 1000 RPS load, Varnish achieves 99% HIT, while FastCGI Cache hovers around 70%.
Varnish Conflicts with Bitrix and Their Solutions
Why Varnish conflicts with Bitrix
Main conflict points: authorization cookies `BITRIX_SM_*`, cart cookie `BX_BASKET_ADD`, admin panel `^/bitrix/`, POST requests, and HTTPS. For HTTPS we add an extra layer: client -> Nginx (SSL termination) -> Varnish -> Nginx. In VCL we forbid caching for `/bitrix/`, POST requests, and when `BITRIX_SM_UIDH` is present. Analytics cookies (`_ga`, `_gid`, `_ym_uid`) are removed — they don't affect content. If no cookies remain after cleaning, we remove the `Cookie` header and cache.
For cache invalidation on product publication, we use an OnAfterIBlockElementUpdate handler that sends a PURGE request with a tag. VCL allows PURGE only from 127.0.0.1.
Example VCL snippet for cookie cleanup:
sub vcl_recv {
# Remove service cookies
if (req.http.Cookie) {
set req.http.Cookie = regsuball(req.http.Cookie, "(^|; )(_ga|_gid|_ym_uid|_ym_d|_ym_isad)=[^;]+", "");
if (req.http.Cookie ~ "^;$") {
unset req.http.Cookie;
}
}
}
Comparison: Varnish vs Nginx FastCGI Cache
| Parameter |
Varnish |
Nginx FastCGI Cache |
| Delivery speed |
<1 ms (RAM) |
<5 ms (RAM/disk) |
| VCL flexibility |
Maximum (conditions, headers) |
Medium (simple rules) |
| Tag-based invalidation |
Built-in (PURGE) |
Via third-party modules |
| Grace + Stale |
Yes (grace mode) |
Yes (stale-while-revalidate) |
| SSL termination |
No (needs upstream) |
Yes (built-in) |
| Backend load |
Minimal |
Slightly higher (header passing) |
Varnish wins due to VCL logic and tagged invalidation, ideal for complex Bitrix catalogs.
Setting Up Varnish Cache Invalidation
How cache invalidation works
When a product is updated via the administrative interface, the `OnAfterIBlockElementUpdate` handler in `init.php` sends an HTTP PURGE request to Varnish. In VCL we allow PURGE only from `127.0.0.1` and additionally check the `X-Purge-Token` header. For tagged invalidation, we use the `X-Cache-Tags` header: Varnish clears cache by tag (e.g., `iblock_5`). This allows selective cache clearing only for changed sections, without affecting the entire site.
Step-by-Step Setup Guide
-
Analysis — Study site structure, page types, cache size, current performance. (1-2 hours)
-
VCL design — Write rules for static files, HTML, exceptions (admin, cart, personal account). (2-4 hours)
-
SSL termination — Configure Nginx before Varnish or HAProxy with certificates. (1 hour)
-
Implementation — Deploy Varnish, test on a site copy. (2-4 hours)
-
Invalidation — Add event handlers in
init.php, tag pages. (2-3 hours)
-
Composite integration — If needed, disable Varnish cache for HTML or set up exceptions. (1-2 hours)
-
Monitoring — Enable
X-Cache logging (HIT/MISS), set up alerts on failure. (1 hour)
-
Load testing — Measure RPS, response time, HIT percentage. (1-2 hours)
What's Included in the Setup
-
Documentation — Complete VCL configuration and architecture document
-
Access — Monitoring dashboards and alerting setup
-
Training — 1-hour session for your team on cache management
-
Support — 30 days of post-setup support and troubleshooting
-
Guarantee — 30% performance improvement or your money back
Timelines and Cost
Setting up Varnish for Bitrix takes from 4 to 16 hours depending on project complexity (Composite presence, number of servers, non-trivial business processes). Typical setup cost ranges from $500 to $1500 depending on complexity, with a payback period of less than 3 months due to server load reduction. Cost is calculated individually — we estimate the scope during a free consultation. Request a consultation with a Bitrix performance engineer.
Useful Links
Order Varnish setup — your site will become 5-10 times faster without code changes.
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.