Optimizing large dataset retrieval using QueryBuilder pagination

When managing large datasets in TYPO3 using the Doctrine DBAL-based QueryBuilder, developers typically rely on setFirstResult() and setMaxResults() to implement offset-based pagination. While this effectively bounds the result set at the SQL level, it introduces potential performance bottlenecks as the offset increases.

In environments with millions of records, deep pagination can lead to significant latency because the database must still scan through the skipped rows. There is a need to determine if TYPO3 provides a native abstraction for keyset pagination (seek method) to avoid the performance degradation associated with high offset values.

Which strategies are recommended within the TYPO3 Database API to implement stable, high-performance pagination for massive tables without relying on OFFSET? Does the current QueryBuilder support a native mechanism for keyset-based retrieval?