Question

An e-commerce reporting service queries a Cosmos DB container with millions of order documents. The query returns thousands of matching results, but the frontend displays only 50 items per page. Currently the code executes the query, materializes the entire result set into memory, and slices out 50 items per request — consuming large amounts of RUs and memory on every page load. You must minimize RU cost and memory usage while preserving the ability to fetch subsequent pages. What should you do?

Accepted Answer

Set MaxItemCount to 50 on the query request options and use the continuation token returned by each FeedResponse to fetch the next page.

Answer

Add an OFFSET 50 LIMIT 50 clause that increases the offset for each page and re-run the full query per page.

Answer

Enable the integrated cache so the full result set is served from the dedicated gateway on every page request.

Answer

Create a composite index on the queried properties so the entire result set is returned with fewer RUs.