Skip to main content

Indexing and testing results

Which index to rebuild​

Configure zorka.search using the module's own rebuild on Индексация и проверка (Indexing and testing). Native Bitrix search reindexing does not replace it. The module also updates the metadata needed by standard results through Bitrix APIs during its pass.

After uninstalling, perform a full rebuild of native Bitrix search.

Run in the admin panel​

  1. Save catalog and field settings.
  2. Open Indexing and testing. Counters show documents, index records and queued changes; dates show the latest product and section passes.
  3. Select Всё (All), Только товары (Products only) or Только разделы (Sections only).
  4. Select 30, 100, 300 or 1000 objects per step; the default is 300.
  5. Click Переиндексировать (Reindex) to start a new pass, or Продолжить (Continue) to resume an unfinished one.
  6. Wait for completion, then use Проверить выдачу (Test results).

Each scope has its own progress. You can interrupt products, process sections, and then resume products. Switch scopes after the current step completes and reload the page. Section passes do not rebuild products, and vice versa. The overall rebuild-needed status is cleared only when both types are ready for the current settings.

The working index is not deleted in full before a pass. Objects update in batches; this is not an atomic switch of the entire catalog to a new snapshot. Restart the affected pass after changing fields or catalogs.

Performance and large catalogs​

Larger batches reduce HTTP requests and can be changed during a pass. A web step stops between objects after about five seconds, or sooner with a lower PHP execution limit. Batch size is a maximum, not a promise to process that many objects per request. One object and final cleanup can take longer.

For large catalogs use CLI or cron, which loads Bitrix once per process. Parallel workers are not implemented. Speed depends on properties, values, database performance and native metadata updates; a larger batch does not guarantee a proportional speedup.

New and changed products​

Changes to products, properties, sections and barcodes made through supported Bitrix APIs enter a queue. It is processed at page completion, before search, and by an agent with a 60-second interval. Large imports may appear gradually; monitor the pending-update counter.

If site agents run on cron, the native Bitrix cron must be working. zorka.search's full-rebuild schedule does not reconfigure it. Direct SQL database writes bypass events and require a rebuild.

Test queries​

  • For an exact string article number: check 000123 and 123 separately.
  • For a section name in substring mode: пушки should find «Тепловые пушки».
  • For phrase synonyms: айфон 15 should find a product named iphone 15.
  • After disabling a field: a query present only in that field should no longer produce a direct match.

Repeat in the storefront and CRM under the intended user. Their filters and presentation may differ from the admin test.