What a 1C-Bitrix site really needs from its hosting

1C-Bitrix is not a CMS you unpack on any PHP hosting and forget about. It is a large framework with its own expectations of the server, and the vendor documents them as a reference environment: BitrixVM is a ready-made virtual machine, BitrixEnv is the same environment installed by a script on a clean Linux system. You do not have to run either of them, but together they are the best specification of what the platform wants — nginx in front of Apache or PHP-FPM, a specific set of PHP extensions, a tuned MySQL, memcached or Redis, and cron. A good Bitrix host reproduces that environment instead of dropping Bitrix onto an ordinary shared stack.

On the PHP side, the checks that fail most often are simple ones. memory_limit should be at least 256 MB, and 512 MB is safer for imports and for working with the catalogue in the admin panel. max_input_vars needs to be around 10 000, or large forms such as access rights and product properties are silently truncated. OPcache must be on, with enough memory for the thousands of files in the core. mbstring.func_overload must be off on current versions, and the charset should be UTF-8. For MySQL, the key values are innodb_buffer_pool_size, sized so the hot part of the database fits in memory, a non-strict sql_mode, which Bitrix expects, and a slow-query log that someone actually reads.

The platform has its own way of grading a server: the Performance Monitor from the perfmon module, “Монитор производительности” in Russian admin panels. Its configuration test runs a fixed set of PHP, file-system and database operations and returns a single score. The number is relative — higher is better, and it is meant to be compared with the vendor’s reference figures and with your own earlier runs, not read as an absolute. Run the test several times at different hours: a score that swings widely points to a noisy neighbour or a throttled disk. Just as useful are the tabs with PHP, database and Bitrix settings, where every deviation from the recommendations is highlighted in red.

Most of Bitrix’s speed comes from caching. Switch on composite site mode, so the static part of each page is served ready-made and only personal blocks such as the cart are loaded dynamically. Move the managed cache from files to memcached or Redis in .settings.php — on a large catalogue, thousands of small cache files on disk become a bottleneck of their own. Then take the agents off hits. By default Bitrix runs background tasks — mailings, search reindexing, exchange steps — during visitors’ requests, so a random customer pays for them with a slow page. Running agents from cron, with cron_events.php called every minute, ends that lottery.

Exchange with 1C is the heaviest thing most Bitrix sites do. The accounting system uploads CommerceML XML files — catalogue, prices, stock — that easily grow to hundreds of megabytes, and the site imports them step by step. Each step has to fit within the step duration set in the catalogue module, within max_execution_time and within the web server’s timeouts; otherwise 1C reports an error and retries the exchange in a loop. Memory matters just as much: parsing a large offers file with a low memory_limit ends in a fatal error halfway through. Leave disk space for archives and unpacked files, raise upload_max_filesize and post_max_size, and schedule full exchanges for the night.

Resources follow the type of project more than the traffic figure. A corporate site with a few hundred pages and a contact form runs comfortably on 2 vCPU and 4 GB of RAM — the Bitrix Start plan. An online shop with live orders, a catalogue of tens of thousands of items and regular 1C exchanges needs headroom so imports can run alongside customers; that is what Bitrix Shop with 4 vCPU and 8 GB is for. A B2B portal with personal price lists, several warehouses and heavy integrations belongs on Bitrix Enterprise with 8 vCPU and 24 GB. Every 1C-Bitrix hosting plan includes a staging copy, which you will want before each platform update.

Finally, choose the licence and the hosting together, because the edition defines the workload. A Start licence covers one site with basic modules; an online shop needs at least Business, with payments and delivery; multi-site setups and web clusters call for Enterprise. A shop-sized plan for a Start licence is money wasted, and an Enterprise portal on a small plan wastes the licence. At WebHostFlow you can buy a 1C licence alongside the hosting: the key is issued to your account, activated on the site by support, renewed on the same invoice, and moving to a larger edition later costs only the difference.