Updating indexer behaviors

By design indexers may show as idle if other jobs are in queue and run times are not predictable since this may vary based on workload and document size and complexity.

Author: gmndrg

articles/search/search-indexer-overview.md

@@ -8,7 +8,7 @@ author: HeidiSteen
 ms.author: heidist
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 06/06/2022
+ms.date: 07/08/2022
 ---
 
 # Indexers in Azure Cognitive Search
@@ -19,6 +19,7 @@ Indexers are cloud-only, with individual indexers for [supported data sources](#
 
 You can run indexers on demand or on a recurring data refresh schedule that runs as often as every five minutes. More frequent updates require a ['push model'](search-what-is-data-import.md) that simultaneously updates data in both Azure Cognitive Search and your external data source.
 
+
 ## Indexer scenarios and use cases
 
 You can use an indexer as the sole means for data ingestion, or in combination with other techniques. The following table summarizes the main scenarios.
@@ -130,6 +131,8 @@ After the first indexer run, you can rerun it on demand using [Run Indexer](/res
 
 You can monitor [indexer status in the portal](search-howto-monitor-indexers.md) or through [Get Indexer Status API](/rest/api/searchservice/get-indexer-status). You should also [run queries on the index](search-query-create.md) to verify the result is what you expected.
 
+Indexers don't have dedicated processing resources. Based on this, indexers' status may show as idle before running (depending on other jobs in the queue) and run times may not be predictable. Other factors define indexer performance as well, such as: document size, document complexity, image analysis, among others.
+
 ## Next steps
 
 Now that you've been introduced to indexers, a next step is to review indexer properties and parameters, scheduling, and indexer monitoring. Alternatively, you could return to the list of [supported data sources](#supported-data-sources) for more information about a specific source.