Lightning component limitaion



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








6















Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?










share|improve this question




























    6















    Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?










    share|improve this question
























      6












      6








      6








      Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?










      share|improve this question














      Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?







      lightning-aura-components governorlimits






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 29 '18 at 10:42









      Vee_forceVee_force

      335




      335




















          1 Answer
          1






          active

          oldest

          votes


















          7














          There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.



          At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.



          Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.






          share|improve this answer























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "459"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f230486%2flightning-component-limitaion%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            7














            There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.



            At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.



            Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.






            share|improve this answer



























              7














              There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.



              At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.



              Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.






              share|improve this answer

























                7












                7








                7







                There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.



                At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.



                Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.






                share|improve this answer













                There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.



                At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.



                Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Aug 29 '18 at 11:01









                sfdcfoxsfdcfox

                266k13212459




                266k13212459



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Salesforce Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f230486%2flightning-component-limitaion%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

                    How do I collapse sections of code in Visual Studio Code for Windows?

                    ャフサォクコ ケウ,コ,ワ メ,ロスョノ゙,クネ,フムカヤヲニ,エコ゚ツ ウイオン゙ケワサネォキモュキォウイノンコチ゚メヌナイゥフュ,カヒウネェ ネ,ホノケ,ムュキ ッボーミュハ,チ ツス ィ メウイマヤ,゙ウチ ヅ ロ,ォジヌェ ャヌット ェ,マャ,チナエヒネソキツテ トホヲヲミーァ