Performance Issues with Tables on Large Datasets

[MichelBalrine]

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?

[Aveyron-RetD]

I think it is known issue #1508
Is it the priority. I do not know.

[MichelBalrine]

I'm very limitated in my case, and I'm ready to paid to see this performance issue solved.

[mammique]

I'm very limitated in my case, and I'm ready to paid to see this performance issue solved.

Me too, my team and I could gather some bounty money to fix this ASAP, this is a very blocking bottleneck for the usability and adoption of the app. Can someone take the job?

[blizzz]

Also related: #1490

Might be we have another issue that could count as duplicate, but not seeing it after quick look.

[janluk22]

I'm very limitated in my case, and I'm ready to paid to see this performance issue solved.

Me too, my team and I could gather some bounty money to fix this ASAP, this is a very blocking bottleneck for the usability and adoption of the app. Can someone take the job?

I could find other contributors if it can help. You are not the only one who meet this issue !

[Aveyron-RetD]

See #2174
Text app in next Version 32.0.3 (due to land the 11/12/25) will have an improvement for rich-text fields nextcloud/text#7980
Thanks for updating this bug report to see if it improves the loading of your tables !

[mammique]

See #2174 Text app in next Version 32.0.3 (due to land the 11/12/25) will have an improvement for rich-text fields nextcloud/text#7980 Thanks for updating this bug report to see if it improves the loading of your tables !

Hi, how long (or how much money) do you evaluate the coding to fix this issue definitely? I know other people stuggling with this, we could gather coding power and/or money to get it done.

Thanks,

Camille.

[MichelBalrine]

Hi !
Good news : I have tested this PR : #2174 and the performances have been globally improved by 40/50% !
It is not a final issue because Tables should be restructured deeper to be able to manage large datasets, but the we can breathe a little bit !

So what about a solution about restructuring the data management client side ?

[mammique]

Hi ! Good news : I have tested this PR : #2174 and the performances have been globally improved by 40/50% ! It is not a final issue because Tables should be restructured deeper to be able to manage large datasets, but the we can breathe a little bit !

So what about a solution about restructuring the data management client side ?

Hi, we have deployed the lazy Vue.js patch for a large number of users, we confirm the improvement. Thanks a lot! We are motivated to kill the remaining 50% of performance bottleneck :-)

Bests,

Camille.