TYPO3 Core

How could we handle that? As a first step maybe load only the first X records (additional setting in TCA to choose how many?), show how many records there really are and offer a link in the record to load them all? That would at least lower the performance-impact when editing other fields. But to edit even larger amounts of IRRE-records we'd still need proper paging and maybe even searching.

I can't imagine where I need more relations. I am not sure if the Cms needs to cover this edge case...

I've got a use case with five fields, each about 20 IRRE records (Monday-Friday with items). This setup is hardly usable with long loading times (10+ seconds) for opening the record (all items collapsed).

Any hints or tips how to improve loading time? Thinking about splitting into smaller pieces.

I'm interested in this too.

We have a setup where the IRRE records has about 900 entries. The backend is unusable with those records enabled.

Luckily for us I can just hide them as those are not needed all the time.
But having a pagination for IRRE records would make things easier.

Thanks