Dash DataTable pagination mode conflict for datasets exceeding one thousand rows

Dash DataTable defaults to client-side pagination, rendering up to approximately five hundred rows efficiently. Beyond this threshold, browser memory usage increases significantly and rendering may stall or become unresponsive. Server-side pagination requires explicit callback logic using page_current and page_size inputs to fetch and display data subsets, but the component does not auto-detect dataset size or initiate server calls automatically. For datasets exceeding one thousand rows, no automatic hybrid mode exists, leaving the choice between client-side and server-side pagination as a manual trade-off between latency, state persistence, and data freshness.

What criteria should guide the selection of pagination mode for a given dataset size? How can state persistence be maintained when switching between client-side and server-side modes? Is there a pattern to automatically transition from client-side to server-side pagination at a defined row threshold without breaking existing callbacks?