Node Load performance












4















I have a small question.



If I use Node::Load on the route of the same node for example:
I go to site.com/node/125 and in preprocess I use Node::Load(125), would Drupal load that node all over again? Or is there some part in the code where it loads it without any performance impact?










share|improve this question





























    4















    I have a small question.



    If I use Node::Load on the route of the same node for example:
    I go to site.com/node/125 and in preprocess I use Node::Load(125), would Drupal load that node all over again? Or is there some part in the code where it loads it without any performance impact?










    share|improve this question



























      4












      4








      4


      1






      I have a small question.



      If I use Node::Load on the route of the same node for example:
      I go to site.com/node/125 and in preprocess I use Node::Load(125), would Drupal load that node all over again? Or is there some part in the code where it loads it without any performance impact?










      share|improve this question
















      I have a small question.



      If I use Node::Load on the route of the same node for example:
      I go to site.com/node/125 and in preprocess I use Node::Load(125), would Drupal load that node all over again? Or is there some part in the code where it loads it without any performance impact?







      nodes






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 21 at 11:23









      Jdrupal

      2,0752726




      2,0752726










      asked Jan 21 at 10:39









      FadyFady

      232




      232






















          2 Answers
          2






          active

          oldest

          votes


















          4














          Entities are statically cached in memory, so there is no performance impact if you load the same entity multiple times within the same request.






          share|improve this answer































            3














            Actually there is no reason to load the node on all node pages.



            When using MYTHEME_preprocess_node you have $variable['node'] that is the loaded node.






            share|improve this answer


























            • yes i know but sometimes I am using other hooks on a page where a node is already loaded (a block for example) and I have no access for the node, so I take the current url and get the node ID from it, and then I use that ID to load the node.

              – Fady
              Jan 22 at 9:54











            • Ok, it was just because you wrote that you loaded it in your preprocessing, then I just wanted to tell that was unnecessary, ;)

              – Jdrupal
              Jan 22 at 9:56











            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "220"
            };
            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%2fdrupal.stackexchange.com%2fquestions%2f275445%2fnode-load-performance%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            4














            Entities are statically cached in memory, so there is no performance impact if you load the same entity multiple times within the same request.






            share|improve this answer




























              4














              Entities are statically cached in memory, so there is no performance impact if you load the same entity multiple times within the same request.






              share|improve this answer


























                4












                4








                4







                Entities are statically cached in memory, so there is no performance impact if you load the same entity multiple times within the same request.






                share|improve this answer













                Entities are statically cached in memory, so there is no performance impact if you load the same entity multiple times within the same request.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 21 at 11:00









                4k44k4

                51.9k560103




                51.9k560103

























                    3














                    Actually there is no reason to load the node on all node pages.



                    When using MYTHEME_preprocess_node you have $variable['node'] that is the loaded node.






                    share|improve this answer


























                    • yes i know but sometimes I am using other hooks on a page where a node is already loaded (a block for example) and I have no access for the node, so I take the current url and get the node ID from it, and then I use that ID to load the node.

                      – Fady
                      Jan 22 at 9:54











                    • Ok, it was just because you wrote that you loaded it in your preprocessing, then I just wanted to tell that was unnecessary, ;)

                      – Jdrupal
                      Jan 22 at 9:56
















                    3














                    Actually there is no reason to load the node on all node pages.



                    When using MYTHEME_preprocess_node you have $variable['node'] that is the loaded node.






                    share|improve this answer


























                    • yes i know but sometimes I am using other hooks on a page where a node is already loaded (a block for example) and I have no access for the node, so I take the current url and get the node ID from it, and then I use that ID to load the node.

                      – Fady
                      Jan 22 at 9:54











                    • Ok, it was just because you wrote that you loaded it in your preprocessing, then I just wanted to tell that was unnecessary, ;)

                      – Jdrupal
                      Jan 22 at 9:56














                    3












                    3








                    3







                    Actually there is no reason to load the node on all node pages.



                    When using MYTHEME_preprocess_node you have $variable['node'] that is the loaded node.






                    share|improve this answer















                    Actually there is no reason to load the node on all node pages.



                    When using MYTHEME_preprocess_node you have $variable['node'] that is the loaded node.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Jan 21 at 11:18

























                    answered Jan 21 at 10:44









                    JdrupalJdrupal

                    2,0752726




                    2,0752726













                    • yes i know but sometimes I am using other hooks on a page where a node is already loaded (a block for example) and I have no access for the node, so I take the current url and get the node ID from it, and then I use that ID to load the node.

                      – Fady
                      Jan 22 at 9:54











                    • Ok, it was just because you wrote that you loaded it in your preprocessing, then I just wanted to tell that was unnecessary, ;)

                      – Jdrupal
                      Jan 22 at 9:56



















                    • yes i know but sometimes I am using other hooks on a page where a node is already loaded (a block for example) and I have no access for the node, so I take the current url and get the node ID from it, and then I use that ID to load the node.

                      – Fady
                      Jan 22 at 9:54











                    • Ok, it was just because you wrote that you loaded it in your preprocessing, then I just wanted to tell that was unnecessary, ;)

                      – Jdrupal
                      Jan 22 at 9:56

















                    yes i know but sometimes I am using other hooks on a page where a node is already loaded (a block for example) and I have no access for the node, so I take the current url and get the node ID from it, and then I use that ID to load the node.

                    – Fady
                    Jan 22 at 9:54





                    yes i know but sometimes I am using other hooks on a page where a node is already loaded (a block for example) and I have no access for the node, so I take the current url and get the node ID from it, and then I use that ID to load the node.

                    – Fady
                    Jan 22 at 9:54













                    Ok, it was just because you wrote that you loaded it in your preprocessing, then I just wanted to tell that was unnecessary, ;)

                    – Jdrupal
                    Jan 22 at 9:56





                    Ok, it was just because you wrote that you loaded it in your preprocessing, then I just wanted to tell that was unnecessary, ;)

                    – Jdrupal
                    Jan 22 at 9:56


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Drupal Answers!


                    • 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%2fdrupal.stackexchange.com%2fquestions%2f275445%2fnode-load-performance%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

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    Npm cannot find a required file even through it is in the searched directory