# Cumulocity IoT Tips and Tricks - Improving microservice performance through larger page sizes

**URL:** <https://community.cumulocity.com/t/cumulocity-iot-tips-and-tricks-improving-microservice-performance-through-larger-page-sizes/5852>\
**Category:** Knowledge Base\
**Tags:** devops, cumulocity\
**Created:** [March 6, 2019, 2:35pm UTC](https://community.cumulocity.com/t/cumulocity-iot-tips-and-tricks-improving-microservice-performance-through-larger-page-sizes/5852 "2019-03-06T14:35:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Welsing](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@Michael\_Welsing](https://community.cumulocity.com/u/Michael_Welsing)\
**Post date:** [March 6, 2019, 2:35pm UTC](https://community.cumulocity.com/t/cumulocity-iot-tips-and-tricks-improving-microservice-performance-through-larger-page-sizes/5852/1 "2019-03-06T14:35:17Z")

</div>

When you query chunks of data using "GET", you will get by default five entries in a chunk -- see [http://cumulocity.com/guides/reference/rest-implementation#-a-name-paging-a-query-result-paging](http://cumulocity.com/guides/reference/rest-implementation#-a-name-paging-a-query-result-paging). This is done to not overload smaller or embedded clients.

If you have a more powerful client, such as a microservice, we recommend increasing the page size as much as possible. This will, instead of running many requests with small results, run a few larger requests with larger results, with a better overall performance. For example, in the Java client, use the "get"-Method of PagedCollectionResource that permits you to pass a pageSize parameter as first argument, and use, for example, the value 2000 to set the maximum page size.