Profiling PHP Code in 1C-Bitrix (Xdebug, Blackfire)

We often encounter situations where a Bitrix site loads in 4–6 seconds, even though nginx and MySQL are fine. PHP spends the lion's share of time on unclear operations. Without a profiler, it's guesswork. With a profiler, exact numbers: which function, how many times called, how long it took. Let's break down two working tools—Xdebug and Blackfire—and show how to find and eliminate bottlenecks. Based on our experience (10+ years, 500+ projects), we guarantee transparent results. Budget savings on development after optimization can reach 50,000–200,000 ₽ depending on complexity.

Why Profiling Is Critical for Bitrix

In complex catalogs with thousands of information blocks and components, performance degrades unnoticed. One page might call CIBlockElement::GetList() 40 times without caching. Or an agent recalculates carts every 5 minutes. Without a profiler, such issues take hours to find. With a profiler, 10 minutes for a measurement and you immediately know where to look. Developer time savings up to 70%.

Xdebug: Profiling via cachegrind

Xdebug is a PHP extension that records traces in cachegrind format. The file is opened in KCachegrind or QCacheGrind. Installation and configuration:

pecl install xdebug
# or apt-get install php8.2-xdebug

# php.ini or 99-xdebug.ini
[xdebug]
zend_extension=xdebug.so
xdebug.mode=profile
xdebug.output_dir=/tmp/xdebug
xdebug.profiler_output_name=callgrind.out.%p.%r
xdebug.start_with_request=trigger

start_with_request=trigger enables profiling only via GET parameter ?XDEBUG_PROFILE=1 or cookie. Do not enable always on production—overhead is 10–20x. According to Xdebug documentation, profiling mode is intended for development, not production servers (xdebug.org/docs/profiler).

Profiling a request:

curl "https://site.ru/catalog/product/?XDEBUG_PROFILE=1" -o /dev/null

A file callgrind.out.* appears in /tmp/xdebug. Open it in KCachegrind—call tree and percentage time per function.

What to Look for in a Bitrix Profile

Typical bottlenecks visible in cachegrind:

• CIBlockElement::GetList()—called dozens of times without cache. Total time >30% indicates component caching issues.
• CSQLWhere::GetQuery()—complex filters without indexes.
• CBitrixComponent::includeComponent()—20+ nested components accumulate overhead.
• CUser::IsAuthorized()—not cached between calls.
• \Bitrix\Main\ORM\Query\Query::exec()—fetchAll() on large selections without limit.

Which Tool to Choose: Xdebug or Blackfire?

Blackfire runs 5–10x faster than Xdebug on production and is suitable for continuous profiling. Xdebug is better for deep analysis on a dev server.

Blackfire: Profiling with Aggregation

Blackfire is a SaaS solution. Agent on server, PHP extension intercepts execution, data goes to blackfire.io. Installation and configuration:

wget -O - https://packages.blackfire.io/gpg.key | apt-key add -
echo "deb http://packages.blackfire.io/debian any main" > /etc/apt/sources.list.d/blackfire.list
apt-get update && apt-get install blackfire blackfire-php

# php.ini
extension=blackfire.so
blackfire.agent_socket=tcp://127.0.0.1:8307

# Authorization
blackfire agent:config --server-id=XXXX --server-token=YYYY
blackfire agent:start

Running profiling:

# CLI
blackfire run php artisan bitrix:some-command

# Via curl
blackfire curl https://site.ru/catalog/

# Via Blackfire browser extension—click "Profile" on the page.

Practical Optimization Algorithm

Why Profiling Should Be Done on a Dev Server?

Xdebug adds significant latency (10–20x), so its use on a production server is unacceptable. Even Blackfire with low overhead can affect real users. A dev server with a copy of the data provides accurate measurements without business risk. If the production server is not available for profiling, we set up staging with data synchronization. Contact us for details on environment setup.

How to Read a cachegrind Profile

KCachegrind shows a call tree where each node is a function with execution time (self vs inclusive). Look for functions where inclusive time exceeds 10% of total time. For Bitrix, these are often CIBlockElement::GetList, CSQLWhere::GetQuery, and CUser::IsAuthorized. Enable filter for the bitrix module—it will cut off all PHP core functions. Order profiling and get a detailed analysis from our engineers.

Profiling Agents and CLI

For background agents and CLI scripts, use XDEBUG_MODE=profile or blackfire run. Example:

XDEBUG_MODE=profile php /path/to/script.php
blackfire run php /path/to/script.php

This helps identify slow agents that drag down background performance.

What's Included in Our Work

• Setting up Xdebug and/or Blackfire on a dev server or staging environment.
• Profiling 3–5 key pages/scripts.
• Detailed report with call graphs and timings.
• Recommendations for optimization (caching, indexes, refactoring).
• Re-profiling after implementing fixes.
• Final documentation and team consultation.

Timeline

Pricing is individual based on scope. We guarantee transparency—you get not just a report, but fixed bottlenecks and measurable performance improvement. Contact us for a project assessment—we'll define the work scope and propose a profiling plan. Order profiling and see the effectiveness.

Additional resources: Profiling (programming) and Xdebug. According to Xdebug documentation, profiling mode is intended for development.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.