Performance Issues with Tables on Large Datasets

Hello,
I’m using Tables 1.0.1 with around 2,000 records, and about 150 new entries are added each month.
Each row contains varying amounts of data, including some rich-text fields with multi-line content.
For some time now, view loading has been getting slower, especially since the update to version 1.0.0, though performance issues had already started appearing before that.
The problem seems to be client-side rather than server-side (Nextcloud hosting).
A segmented view only slightly improves performance, which is becoming a real daily issue.
From what I understand (but I'm maybe wrong), the entire table’s data appears to be loaded into client memory, rather than just the data relevant to the current view. This could explain why reducing the number of displayed columns has little effect.
On low-end devices (limited RAM? underpowered CPU?), Tables becomes unusable: searching or editing a row simply freezes.

Are these limitations known, and are there planned improvements to support larger datasets more efficiently?

Start by reproducing the slowdown with about 2,000 records, rich-text and multi-line fields, then compare loading, searching, and row editing in segmented and unsegmented views. The issue does not name files or tests; completion would require identifying the client-side bottleneck and defining an efficient approach for larger datasets.