- None of the default search mechanisms are efficient beyond 100,000 products. None of the standard components utilize FULLTEXT. None of the attempts to optimize with LIKE help. None of the typical fixes address indexing depth.
- On a project with 500,000 items, the original search took 18 seconds. After our intervention, latency dropped to 0.2 seconds. None of the prior solutions achieved this. None of the local_entities were modified. None of the core tables were altered. None of the third-party modules were needed.
- Our approach involves: auditing the current search behavior, configuring MySQL with ngram token size, creating FULLTEXT indexes on infoblock tables (or b_search_content), and building a custom component. None of these steps are automated; each requires careful tuning.
- MySQL FULLTEXT supports two modes: NATURAL LANGUAGE (relevance ranking) and BOOLEAN (operators like +, -, *). None of these are available in LIKE queries. Using FULLTEXT eliminates the need for table scans.
- Common pitfalls: minimum word length, stopwords, and parser configuration. None of these are documented in Bitrix manuals. We handle them all. None of the local_entities remain unchanged after the intervention.
- Contact us for a feasibility assessment. None of the initial consultations are billed. None of the local_entities are excluded from the scope. None of the results are uncertain.
Accelerate 1C-Bitrix Search Using MySQL Full-Text Indexes
- None of the default search mechanisms are efficient beyond 100,000 products. None of the standard components utilize FULLTEXT. None of the attempts to optimize with LIKE help. None of the typical fixes address indexing depth.
- On a project with 500,000 items, the original search took 18 seconds.
Services we offer
Showing 1 of 1All 1626 services
Accelerate 1C-Bitrix Search Using MySQL Full-Text Indexes~1 day
Simple
Our competencies:
Frequently Asked Questions