Skip to content

Commit 8c43bc3

Browse files
authored
Update search-performance-tips.md
Updated to reflect how regex can affect query performance.
1 parent 76407f9 commit 8c43bc3

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/search/search-performance-tips.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: LiamCavanagh
77
ms.author: liamca
88
ms.service: cognitive-search
99
ms.topic: conceptual
10-
ms.date: 08/25/2022
10+
ms.date: 04/20/2023
1111
---
1212

1313
# Tips for better performance in Azure Cognitive Search
@@ -132,6 +132,11 @@ As this hypothetical scenario illustrates, you can have configurations on lower
132132

133133
An important benefit of added memory is that more of the index can be cached, resulting in lower search latency, and a greater number of queries per second. With this extra power, the administrator may not need to even need to increase the replica count and could potentially pay less than by staying on the S1 service.
134134

135+
### Tip: Consider alternatives to regular expression queries
136+
137+
[Regular expression queries](query-lucene-syntax#bkmk_regex.md) or regex can be particularly expensive. While they can be very useful for complex searches, they also may require a lot of processing power to be executed, especially if the regular expression has a lot of complexity or when searching through a large amount of data. This would result in high search latency. In order to reduce the search latency, try to simplify the regular expression or break the complex query down into smaller, more manageable queries.
138+
139+
135140
## Next steps
136141

137142
Review these other articles related to service performance:

0 commit comments

Comments
 (0)