Issue Feature Closed

#89015Lazy Loading for TCA / Backend View to improve performance

Alex Nostadt 08/26/19, 15:45 updated 11/10/26, 13:32

Description

Hi guys,

especially when having records with several fields and tons of records TCA / Backend View can become extremely slow, even more on dev systems which does not have the power of the production system. When there’s the need to edit such a record (in dev mode) load time can be very long.

Reviews 1

History 22

  1. Alex Nostadt changed subject Lazy Loading for TCA to improve performance Lazy Loading for TCA / Backend View to improve performance <span data-processor="relativetime" data-value="2019-08-26T15:52:57+00:00" > 08/26/19, 15:52 </span>

  2. Rémy DANIEL commented <span data-processor="relativetime" data-value="2020-02-20T09:02:29+00:00" > 02/20/20, 09:02 </span>

    Hello

    Thanks for taking care of creating an issue.

    Could you provide more context to the performance issue that you have?
    Especially TYPO3, php and database version.

    Also, an example extension, with the mentionned TCA would be helpful.

    And an screenshot of the browser’s devtools showing the rendering time of the page (to see if it is a server issue or a browser rendering issue).

    Cheers.

  3. Alex Nostadt commented <span data-processor="relativetime" data-value="2020-02-27T12:51:31+00:00" > 02/27/20, 12:51 </span>

    Providing TCA examples etc. would require more time as I do not want to provide the TCA which is used in a customer project. As I have time, I provide a demo ext. along the Dev-Tool Screenshot. I keep that in mind and hope to be able to provide that somewhen soon. Thus I guess it will not happen within the next months. I am very much up for this feature, yet have other higher priorities atm.

    In the meantime I provide a more in depth description:

    We have a Model “Campaign” which has 5 tabs. In the general tab are a few simple fields and relation to an other Model “CampaignValue”. Editors can CRUD “CampaignValue”-Records to schedule Record-Updates. It also includes a “CampaignValue”-History-Table. As manual changes of “Campaign” leads to a new “CampaignValue”-Entry this list can become quite long over the time. Further, each Campaign is associated to a “Product” and in the Campaign selected “Product”-Data can be overwritten. Nowadays a lot of fields can be overwritten. These fields are RTE, IRRE, 1:n relations and simple fields such as input. The Model Product has a bunch of tabs and relations either, yet I guess the Campaign example is fine.

    I hope so far you get what I am talking about.

    —————-

    All the data needs to be loaded, yet not every may be required when we want to edit a record. Let’s say we only want to change a few properties, only these would require being loaded. So, for example all of these are on the first tab, then only the first tab is loaded upon opening the record. Then we do our changes, hit save and are good to go.

    Of course, if there’re displayConds, these needs to be considered by a lazyload feature. I assume there’s more to consider. I rate the complexity to medium / hard.

    We’re also making quite heavy usage of the bookmark-feature to access our test records quickly. So, we end up in the regular TCA Edit-View always. Hence, I am aware of the option to edit selected properties via TCA-List-View.

    —————-

    Here are a few ideas:

    - Lazyload needs to be enabled per table.
    - Lazyload can be enabled for certain fields
    - Lazyload can be enabled for tabs

    —————-

    An other reason for this feature:
    T3 BE allows editor to work on their mobile phones already. Loaded content can be reduced and therefore editors can work more fast via mobile phones.

  4. Christian Eßl commented <span data-processor="relativetime" data-value="2020-03-03T08:48:38+00:00" > 03/03/20, 08:48 </span>

    Do you have more info about the structure of the TCA and their inline elements?
    For example, one known performance bottleneck happens when you have a TCA table with 1:n IRRE relations to another TCA table and that child tables “label” in the TCA isn’t a simple db field of the same table, but for example the relation field to its parent. Something like:

    // TCA config of the 1:n irre child
    return [
        'ctrl' => [
            'label'                    => 'title',
            'label_alt'              => 'tt_content', // the relation field to its parent table
            'label_alt_force'.    => true,
            'sortby'                   => 'sorting',

    TYPO3 would then automatically look up the label of the parent table from the “tt_content” relation field and show it in the TCEForm for the children elements. But this could easily turn into a performance bottleneck in several cases. For example, the “l10n_parent” selects would then all need create many similar db calls to fetch these labels from the foreign table and this would easily blow up the number of db calls in the backend for each new 1:n irre record that is added.

  5. Sybille Peters changed Tags tca, performance, lazy loading tca, performance, lazy loading, large-site <span data-processor="relativetime" data-value="2020-11-24T13:56:28+00:00" > 11/24/20, 13:56 </span>

  6. Benni Mack commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2024-12-11T14:55:31+00:00" > 12/11/24, 14:55 </span>

    Yes, I’m keen on getting more feedback to this topic. I also don’t fully understand the term “Backend View”. Is this the Form View or FormEngine Editing interface, or the Page module?

  7. Simon Schaufelberger commented <span data-processor="relativetime" data-value="2024-12-11T15:14:08+00:00" > 12/11/24, 15:14 </span>

    I’m also having this issue with a frontend user record for example. Once you click on editing the fe_user record, there are related records with several 1000 records as a dropdown field for example. Imagine a frontend user that has a company that you can select. In this case the dropdown is not the best option to choose a record (but only one can be selected, so the “group” is also not optimal).

    In Laravel Nova (payed product) exists a way to define a relationship as searchable. That will create a searchable dropdown: https://nova.laravel.com/docs/resources/relationships#searchable-relations

    I have an old version of nova and could give insights in how they implemented this. This would definitely be a killer feature for TYPO3!

    In general we could get a lot of inspirations from Laravel Nova.

  8. Garvin Hicking commented <span data-processor="relativetime" data-value="2024-12-11T16:27:34+00:00" > 12/11/24, 16:27 </span>

    @simonschaufi We do have a “suggestWizard” that would probably be usable? The technique should be pretty straight-forward, I doubt we will need to rip it out of any other system. ;)

    It’s “just” REST- and UI-legwork… and I do agree, optimizing this would be great to have.

  9. Simon Schaufelberger commented <span data-processor="relativetime" data-value="2024-12-11T16:31:14+00:00" > 12/11/24, 16:31 </span>

    Yes, we do have a suggestWizard but that is not usable for dropdown values (single values), or? I just don’t want to misuse a group field for that and set max to 1.

  10. Benni Mack commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-11-09T17:36:48+00:00" > 11/09/26, 17:36 </span>

    Closing this one: there has been no feedback since 2020 and the request is too unspecific to act on. FormEngine already lazy-loads collapsed inline (IRRE) children — their fields are only rendered via AJAX when expanded — which covers the main scenario described (long 1:n child lists). Lazy loading of whole tabs or single fields would need a concrete, reproducible example to be evaluated.

    The concrete edit-form performance regression is tracked in #109180, large-site issues in general in #93547. A searchable single-select for relations with many items (comment by Simon) would be a good separate feature request — feel free to open one.

    If you still experience this with a current version, please open a new issue with a minimal TCA example and timings.

  11. Benni Mack commented <span data-processor="relativetime" data-value="2026-11-09T17:38:13+00:00" > 11/09/26, 17:38 </span>

    btw… #101117 and #81036 landed in v14.x which made a huge difference in the issues you mentioned.

  12. Simon Schaufelberger commented <span data-processor="relativetime" data-value="2026-11-09T17:48:23+00:00" > 11/09/26, 17:48 </span>

    I thought I gave a good example but here is one:

    extend fe_users with a company relation field like:

        'company' => [
            'exclude' => 0,
            'label' => 'company',
            'config' => [
                'type' => 'select',
                'renderType' => 'selectSingle',
                'foreign_table' => 'tx_shop_domain_model_company',
                'items' => [
                    ['label' => '', 'value' => 0],
                ],
                'minitems' => 0,
                'maxitems' => 1,
            ],
        ],
    <?php
    
    return [
        'ctrl' => [
            'title' => 'company',
            'label' => 'name',
            'tstamp' => 'tstamp',
            'crdate' => 'crdate',
            'delete' => 'deleted',
            'enablecolumns' => [
                'disabled' => 'hidden',
            ],
    
            'security' => [
                'ignorePageTypeRestriction' => true,
            ],
        ],
        'types' => [
            '1' => [
                'showitem' => 'name',
            ],
        ],
        'columns' => [
    
            'name' => [
                'exclude' => 0,
                'label' => 'name',
                'config' => [
                    'type' => 'input',
                    'size' => 30,
                    'eval' => 'trim',
                ],
            ],
        ],
    ];

    Create a new company table with a name field and add 10000 records to it. Then open fe_user in the backend. What TYPO3 misses is the possibility to lazy load a single dropdown and not load all 10000 records in the dom

  13. Benni Mack commented and changed status Closed Needs Feedback <span data-processor="relativetime" data-value="2026-11-09T18:00:28+00:00" > 11/09/26, 18:00 </span>

    from a PHP perspective I think we’re in good shape in v14/v15. But: how should a singleSelect with native HTML be loaded natively if you have 1000 entries? This is HTML/DOM/Browser issue IMHO. What you are looking is probably a typeahead? or something like this? https://review.typo3.org/c/Packages/TYPO3.CMS/+/96865

  14. Simon Schaufelberger commented <span data-processor="relativetime" data-value="2026-11-09T19:26:17+00:00" > 11/09/26, 19:26 </span>

    > https://review.typo3.org/c/Packages/TYPO3.CMS/+/96865

    yes! This would be awesome!

    > What you are looking is probably a typeahead?

    Something similar like this ajax loading example: https://select2.org/data-sources/ajax/

  15. Simon Schaufelberger commented <span data-processor="relativetime" data-value="2026-11-10T13:26:47+00:00" > 11/10/26, 13:26 </span>

    I can confirm that loading the Form is MUCH faster in v14 now. Even loading 10800 records takes less than 3 seconds to load the whole page with all assets and 17MB response from the TYPO3 backend.

  16. Garvin Hicking commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-11-10T13:32:05+00:00" > 11/10/26, 13:32 </span>

    I’m closing this, and believe we should carry on with this in #111144