Poor document table rendering performance

[weltenwort]

The current rendering of the document table takes several seconds for just 500 documents, which makes its use with larger datasets impractical.

⚠️ The measurements and goals in this issue are a work in progress and will be expanded over time.

Progress

• measure current performance
• define performance targets

relates to #10682

[foxylion]

In our use case the fetching of data is the most time consuming part of the rendering.

In an ideal case I think it should only fetch the first X records and fetch later on more records.
The first query should not include all possible records, but only the first 50 or so.
Elasticsearch does support continuing the search after the position of the last record (e.g. the 50th):
https://www.elastic.co/guide/en/elasticsearch/reference/master/search-request-search-after.html

[Bargs]

Related #11457

[lizozom]

@timroes @kertal can this be closed? I think this may be resolved.

[kertal]

I think this can be closed since it's referring to the classic table, and it seems it didn't render in 50 patches back in the days? the upcoming new table is virtualizing scrolling anyway. so this issue is news from the last century and should therefore be closed

[timroes]

Also the original issue is 4 years old, so I'd say we're closing it and in case some more specific issues come up we'll open individual more specific issues for those.