If a continuable query returns many rows, one approach
to improve performance is to add more restrictive property conditions
to the search.
Important: The user might not have access to some rows
because of security permissions; these non-accessible rows are automatically
removed from the returned results. Internally, the search is reissued
until the requested page is filled despite any filtering that occurs
because of security permissions. For this reason, do not rely on security
permissions to limit the number of rows that a query returns.
A continuable query might be slow for two main reasons:
- Fetching rows across the network from the database server to the
Content Platform Engine is time consuming. The client eventually obtains
the entire result set by requesting every page of results.
- Finding the rows that satisfy the search conditions might not
occur quickly.