The list command currently uses a unlimited SELECT * FROM c query on containers and limits the results to specified -m value (default is 100) using the SDKs QueryRequestOptions.MaxItemCount setting. We should consider limiting the Query with i.e. SELECT TOP {effectiveMaxItemCount.Value} * FROM c, or at least measure whether both approaches are interchangable with regards to perf and RU cost.
The list command currently uses a unlimited
SELECT * FROM cquery on containers and limits the results to specified -m value (default is 100) using the SDKsQueryRequestOptions.MaxItemCountsetting. We should consider limiting the Query with i.e.SELECT TOP {effectiveMaxItemCount.Value} * FROM c, or at least measure whether both approaches are interchangable with regards to perf and RU cost.