mysqli_free_result() is slow when all the data are not read while using MYSQLI_USE_RESULT












0















I am using MYSQLI_USE_RESULT(Unbuffered query) while querying a huge data from the table.
For testing I took a table of 5.6 GB size.
I selected all columns Select * from test_table.



If I am not reading any rows with method like fetch_assoc() etc. Then try to close the result with mysqli_free_result(). It takes 5 to 10 secs to close it.



Sometimes I read required number rows based on available memory. And then I call mysqli_free_result() it takes less time when compared with not even one row is read.



So lesser unread rows means lesser time to free results. More unread rows more time to free results.



It's no where documented that this functionality will consume time in best of my knowledge.



Time taken for query is around 0.0008 sec.



Is it bug or is it expected behavior?
For me this sluggishness defeating whole point using MYSQLI_USE_RESULT.




MySQL v5.7.21, PHP v7.2.4 used for testing.




Alias of this function are mysqli_result::free -- mysqli_result::close -- mysqli_result::free_result -- mysqli_free_result.










share|improve this question





























    0















    I am using MYSQLI_USE_RESULT(Unbuffered query) while querying a huge data from the table.
    For testing I took a table of 5.6 GB size.
    I selected all columns Select * from test_table.



    If I am not reading any rows with method like fetch_assoc() etc. Then try to close the result with mysqli_free_result(). It takes 5 to 10 secs to close it.



    Sometimes I read required number rows based on available memory. And then I call mysqli_free_result() it takes less time when compared with not even one row is read.



    So lesser unread rows means lesser time to free results. More unread rows more time to free results.



    It's no where documented that this functionality will consume time in best of my knowledge.



    Time taken for query is around 0.0008 sec.



    Is it bug or is it expected behavior?
    For me this sluggishness defeating whole point using MYSQLI_USE_RESULT.




    MySQL v5.7.21, PHP v7.2.4 used for testing.




    Alias of this function are mysqli_result::free -- mysqli_result::close -- mysqli_result::free_result -- mysqli_free_result.










    share|improve this question



























      0












      0








      0








      I am using MYSQLI_USE_RESULT(Unbuffered query) while querying a huge data from the table.
      For testing I took a table of 5.6 GB size.
      I selected all columns Select * from test_table.



      If I am not reading any rows with method like fetch_assoc() etc. Then try to close the result with mysqli_free_result(). It takes 5 to 10 secs to close it.



      Sometimes I read required number rows based on available memory. And then I call mysqli_free_result() it takes less time when compared with not even one row is read.



      So lesser unread rows means lesser time to free results. More unread rows more time to free results.



      It's no where documented that this functionality will consume time in best of my knowledge.



      Time taken for query is around 0.0008 sec.



      Is it bug or is it expected behavior?
      For me this sluggishness defeating whole point using MYSQLI_USE_RESULT.




      MySQL v5.7.21, PHP v7.2.4 used for testing.




      Alias of this function are mysqli_result::free -- mysqli_result::close -- mysqli_result::free_result -- mysqli_free_result.










      share|improve this question
















      I am using MYSQLI_USE_RESULT(Unbuffered query) while querying a huge data from the table.
      For testing I took a table of 5.6 GB size.
      I selected all columns Select * from test_table.



      If I am not reading any rows with method like fetch_assoc() etc. Then try to close the result with mysqli_free_result(). It takes 5 to 10 secs to close it.



      Sometimes I read required number rows based on available memory. And then I call mysqli_free_result() it takes less time when compared with not even one row is read.



      So lesser unread rows means lesser time to free results. More unread rows more time to free results.



      It's no where documented that this functionality will consume time in best of my knowledge.



      Time taken for query is around 0.0008 sec.



      Is it bug or is it expected behavior?
      For me this sluggishness defeating whole point using MYSQLI_USE_RESULT.




      MySQL v5.7.21, PHP v7.2.4 used for testing.




      Alias of this function are mysqli_result::free -- mysqli_result::close -- mysqli_result::free_result -- mysqli_free_result.







      php mysql optimization mysqli database-performance






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 16 '18 at 8:12









      kit

      1,10631017




      1,10631017










      asked Nov 16 '18 at 6:46









      itsoft3gitsoft3g

      3291527




      3291527
























          0






          active

          oldest

          votes












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fstackoverflow.com%2fquestions%2f53332743%2fmysqli-free-result-is-slow-when-all-the-data-are-not-read-while-using-mysqli-u%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f53332743%2fmysqli-free-result-is-slow-when-all-the-data-are-not-read-while-using-mysqli-u%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

          Florida Star v. B. J. F.

          Danny Elfman

          Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues