An Azure service that is used to provision Windows and Linux virtual machines.
The pagesize determines how many results are returned at one time. If the number of results is too large it can result in memory exhaustion on the machine doing the search, or in network traffic congestion, or query failure.
If the results won't fit in a single page, the remaining results will be returned in subsequent pages. This allows your client a chance to start processing the results before the search is complete. Additional pages will be filled and returned from the same query as needed.
This is where pipelining the results of the query is beneficial, rather than simply accumulating the entire set of results and then processing the data stored in the array once the query has finished.
The default is to attempt placing all the results in a single page. That might be appropriate for a reasonably small number of result but lead to failure if the data exceed the default (and unstated!) page size.
If in doubt, try starting with a page size of, say, 500.