Search only in titles

---

Page Size

Larger page sizes generally result in longer response times, so DaaS limits queries to 1,000 records each. However, the impact of page size on response time depends on data complexity, and DaaS optimizes queries to fetch only requested fields. In some cases, such as project graph queries with only required filters, response times may be similar whether requesting 10 or 1,000 records.

query Project {
    project(offset: 0, next: 1000, organizationID: <id>, isDeleted: false) {
        id
        address1
        address2
        city
        county
        postalCode
        countryCode
        name
        projectNumber
        isActive
        currentEstimatedCompletionDate
        currentEstimatedStartDate
        originalEstimatedCompletionDate
        originalEstimatedStartDate
        projectType
        siteName
        stateProvince
        currency
        dateCreated
        dateModified
        segmentID
        segmentDescription
        isDeleted
    }
}

Querying only the id and contract number in the contract graph yields similar performance regardless of the page size.

# page size will have little impact with just a few basic fields to calculate

However, adding complex budget fields or sub-graph objects to a query decreases performance, especially with larger page sizes.

# inclusion of more complex billing and budget values or subgraphs impacts performance particularly for large page sizes

---

Last Published Friday, January 16, 2026