Stress Testing 1C and 1C-Bitrix Exchange

The exchange works fine on a small dataset but breaks under real volumes. We've seen this many times: a test with 1,000 products passes in a minute, but with 50,000 — PHP timeout, memory exhaustion, database deadlocks. Typical symptoms: site goes down, 1C throws an import error, backup restore required. Each exchange failure during peak hours can result in significant lost revenue. Stress testing 1C Bitrix exchange involves loading data close to production volume, fixing bottlenecks, and determining limits before going live. Our turnkey stress testing service includes generating realistic test data, profiling bottlenecks, and implementing optimizations that can improve import speed by 5x or more. Contact us for a free evaluation of your exchange scenario — we assess it within one day. Our team has 10+ years of Bitrix development experience and has performed over 50 stress tests for catalogs ranging from 10,000 to 500,000 SKUs, with 5+ years on the market. Identifying issues during testing saves up to 40% of the budget for urgent fixes. Get a consultation on your exchange — we evaluate your scenario within one day.

Exchange Architecture and Load Points

The standard exchange via CommerceML proceeds step by step:

1C → Export XML (catalog.xml, offers.xml, import.xml)
     ↓
Bitrix → POST /bitrix/admin/1c_exchange.php
          ↓
     Parse XML (SimpleXML / XMLReader)
          ↓
     Write to b_iblock_element, b_iblock_element_property, b_catalog_price

Bottlenecks at 50,000+ SKUs:

• XML parsing — SimpleXML loads the entire file into memory. With a 200 MB file and PHP memory_limit = 256M, you get out of memory. Solution: XMLReader for streaming.
• Database writes — standard CIBlockElement::Add() / CIBlockElement::Update() work row by row. 50,000 elements × 50 ms = 40 minutes just for writing.
• Price recalculation — after each price update, cumulative discounts are recalculated. For batch writes this should be deferred until the end of import.

Why Exchange Breaks on Large Volumes

The main reasons are architectural limitations of standard components. SimpleXML creates an object tree in memory, which for a 200 MB file results in >1 GB consumption. Additionally, CIBlockElement::Add() executes many separate SQL queries (permission checks, events, caching). With 50,000 elements, the number of queries exceeds 500,000, causing database timeouts. PHP memory profiling reveals that SimpleXML causes excessive memory consumption due to loading the entire DOM tree, whereas XMLReader with streaming reduces peak memory usage from 1 GB to under 200 MB.

How We Identify Bottlenecks

class CatalogXmlGenerator
{
    public function generate(int $productCount, string $outputPath): void
    {
        $writer = new \XMLWriter();
        $writer->openUri($outputPath);
        $writer->startDocument('1.0', 'UTF-8');
        $writer->startElement('КоммерческаяИнформация');

        for ($i = 1; $i <= $productCount; $i++) {
            $this->writeProduct($writer, $i);
        }

        $writer->endElement();
        $writer->endDocument();
        $writer->flush();
    }

    private function writeProduct(\XMLWriter $w, int $i): void
    {
        $w->startElement('Товар');
        $w->writeElement('Ид', "product-uuid-{$i}");
        $w->writeElement('Наименование', "Test product #{$i}");
        $w->writeElement('Артикул', "ART-{$i}");
        // ... properties, prices
        $w->endElement();
    }
}

Preparing Test Data

We generate an exchange XML file with realistic volume: as many products, SKUs, and prices as in production plus a 30% buffer.

Measurement Parameters

Typical Findings During Stress Tests

Out of memory when parsing large XML. Fix: replace simplexml_load_file() with XMLReader for streaming:

$reader = new \XMLReader();
$reader->open($filePath);

while ($reader->read()) {
    if ($reader->nodeType === \XMLReader::ELEMENT && $reader->localName === 'Товар') {
        $node = new \SimpleXMLElement($reader->readOuterXml());
        $this->processProduct($node);
        unset($node); // free memory
    }
}

Recommendation from PHP documentation

Deadlocks with concurrent exchange. If a cron exchange runs and a new request from 1C arrives simultaneously, both write to b_iblock_element_property. Fix: use a lock file or write state to b_option:

if (file_exists($lockFile)) {
    throw new \RuntimeException('Import already running');
}
file_put_contents($lockFile, getmypid());

Slow discount recalculation. After bulk price writes, CCatalogDiscount::CountDiscount() is called for each element. With 50,000 SKUs, this is critical. Fix: disable auto-recalculation via the OnBeforeCatalogDiscountCounters event during import, then run recalculation once after completion.

Performance Test of Individual Operations

XMLReader is 5 times more efficient than SimpleXML for large files — evident from parsing time at 10,000 SKUs. Batch writing via ORM is 6 times faster than row-by-row CIBlockElement::Add().

Case Study: Wholesale Supplier, 120,000 SKUs

Problem: Exchange with 1C took 6 hours, failing at 70% due to exceeding max_execution_time.

Work performed:

• Replaced SimpleXML with XMLReader — XML parsing from 40 min to 8 min
• Implemented batch INSERT for properties (500 records per transaction) — writing from 3 hours to 35 min
• Deferred discount recalculation until after import — saved another 40 min
• Split import into chunks of 5,000 elements with checkpoints — eliminated progress loss on error

Result: Full exchange of 120,000 SKUs in 47 minutes, stable for over six months. Time savings — 80%.

What's Included in Exchange Stress Testing

1. Generate test XML files with realistic data volume
2. Measure baseline metrics: time, memory, SQL queries, CPU
3. Profile bottlenecks with optimization recommendations
4. Fix identified issues: XMLReader, batch writing, lock mechanism
5. Retest after optimization with result confirmation
6. Document limits and recommended server settings

Timely identification of issues saves significantly on emergency fixes. We guarantee that after our work the exchange will handle the stated load. Order a stress test and receive a detailed report. We work under a contract with metrics fixed in the protocol. Our turnkey stress testing packages are priced individually. Write to us for a project evaluation and get a detailed cost estimate within one business day.

CommerceML

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.