Filament Table Builder: Pagination performance on large datasets

FilamentPHP leverages the Laravel Eloquent builder to handle record retrieval, utilizing modifyQuery() to apply constraints and standard length-aware pagination to manage result sets.

When dealing with extremely large datasets, the default offset-based pagination may encounter performance degradation as the database scans increasing numbers of rows to reach deeper pages. There is a need to determine the most efficient way to bound these queries without sacrificing the built-in Table Builder functionality.

• Does Filament provide a native mechanism to switch from offset-based pagination to cursor-based pagination within the Table Builder?
• What is the recommended approach to bound a query for high-volume tables to prevent memory exhaustion during eager loading?