Unrealistically increasing amounts of response time taken to fetch items as offsets go higher.

Summary:

I am following the endpoint documented in to fetch TimeRecordGroups. I am using the following URL to fetch the child entity TimeAttributes also using the expand parameter: /hcmRestApi/resources/11.13.18.05/timeRecordGroups?expand=timeAttributes&limit=500&offset=0&onlyData=true&orderBy=timeRecordGroupId%3Aasc&q=timeAttributes.attributeId%20is%20not%20null

I am keeping the expand, limit, orderBy and q parameters the same across requests and moving only the offset parameter by 500 to paginate. I want only those TimeRecordGroups which have at least on child object timeAttributes and achieve that using the q param by filtering on the child's key.

But as the offset values get higher, the API is taking longer response times per page. I've added a table depicting time for a request to complete for different values of offset.