Why mysql remove query cache in 8.0 version?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





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







up vote
1
down vote

favorite












Why mysql remove query cache in 8.0 version ?






mysql query-cache mysql-8.0







share|improve this question





























    up vote
    1
    down vote

    favorite












    Why mysql remove query cache in 8.0 version ?






    mysql query-cache mysql-8.0







    share|improve this question

























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      Why mysql remove query cache in 8.0 version ?






      mysql query-cache mysql-8.0







      share|improve this question















      Why mysql remove query cache in 8.0 version ?






      mysql query-cache mysql-8.0




      mysql query-cache mysql-8.0






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 3 hours ago









      RolandoMySQLDBA

      137k24215365




      137k24215365










      asked 3 hours ago









      shaoyihe

      1112




      1112




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          2
          down vote













          Good riddance !!!



          It is a challenge for most database developers to correctly estimate the size the most common result sets in their applications. Having a large query cache was just a big bandage for that.



          There is a bigger reason that foreshadowed the demise of the query cache. Four years ago, I answered the post Why query_cache_type is disabled by default start from MySQL 5.6?. Is short, the query cache was always inspecting the InnoDB Buffer Pool for changes. You can find this on Pages 209-215 of High Performance MySQL (2nd Edition).



          I mentioned this over the years:




          • Sep 05, 2012 : Is the overhead of frequent query cache invalidation ever worth it?


          • Sep 25, 2013 : invalidating query cache entries(key)


          • Sep 26, 2013 : query cache hit value is not changing in my database


          • Dec 23, 2013 : MySQL with high CPU and memory usage

          RIP Query Cache !!!






          share|improve this answer



























            up vote
            1
            down vote













            There is a detailed blog from the MySQL server team about this, where Matt Lord says:




            The query cache has been disabled-by-default since MySQL 5.6 (2013) as it is known to not scale with high-throughput workloads on multi-core machines.



            We considered what improvements we could make to query cache versus optimizations that we could make which provide improvements to all workloads.



            While these choices themselves are orthogonal, engineering resources are finite. That is to say that we are shifting strategy to invest in improvements that are more generally applicable to all workloads.







            share|improve this answer






















              Your Answer







              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "182"
              ;
              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',
              convertImagesToLinks: false,
              noModals: false,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













               

              draft saved


              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f217577%2fwhy-mysql-remove-query-cache-in-8-0-version%23new-answer', 'question_page');

              );

              Post as a guest

















              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              2
              down vote













              Good riddance !!!



              It is a challenge for most database developers to correctly estimate the size the most common result sets in their applications. Having a large query cache was just a big bandage for that.



              There is a bigger reason that foreshadowed the demise of the query cache. Four years ago, I answered the post Why query_cache_type is disabled by default start from MySQL 5.6?. Is short, the query cache was always inspecting the InnoDB Buffer Pool for changes. You can find this on Pages 209-215 of High Performance MySQL (2nd Edition).



              I mentioned this over the years:




              • Sep 05, 2012 : Is the overhead of frequent query cache invalidation ever worth it?


              • Sep 25, 2013 : invalidating query cache entries(key)


              • Sep 26, 2013 : query cache hit value is not changing in my database


              • Dec 23, 2013 : MySQL with high CPU and memory usage

              RIP Query Cache !!!






              share|improve this answer
























                up vote
                2
                down vote













                Good riddance !!!



                It is a challenge for most database developers to correctly estimate the size the most common result sets in their applications. Having a large query cache was just a big bandage for that.



                There is a bigger reason that foreshadowed the demise of the query cache. Four years ago, I answered the post Why query_cache_type is disabled by default start from MySQL 5.6?. Is short, the query cache was always inspecting the InnoDB Buffer Pool for changes. You can find this on Pages 209-215 of High Performance MySQL (2nd Edition).



                I mentioned this over the years:




                • Sep 05, 2012 : Is the overhead of frequent query cache invalidation ever worth it?


                • Sep 25, 2013 : invalidating query cache entries(key)


                • Sep 26, 2013 : query cache hit value is not changing in my database


                • Dec 23, 2013 : MySQL with high CPU and memory usage

                RIP Query Cache !!!






                share|improve this answer






















                  up vote
                  2
                  down vote










                  up vote
                  2
                  down vote









                  Good riddance !!!



                  It is a challenge for most database developers to correctly estimate the size the most common result sets in their applications. Having a large query cache was just a big bandage for that.



                  There is a bigger reason that foreshadowed the demise of the query cache. Four years ago, I answered the post Why query_cache_type is disabled by default start from MySQL 5.6?. Is short, the query cache was always inspecting the InnoDB Buffer Pool for changes. You can find this on Pages 209-215 of High Performance MySQL (2nd Edition).



                  I mentioned this over the years:




                  • Sep 05, 2012 : Is the overhead of frequent query cache invalidation ever worth it?


                  • Sep 25, 2013 : invalidating query cache entries(key)


                  • Sep 26, 2013 : query cache hit value is not changing in my database


                  • Dec 23, 2013 : MySQL with high CPU and memory usage

                  RIP Query Cache !!!






                  share|improve this answer












                  Good riddance !!!



                  It is a challenge for most database developers to correctly estimate the size the most common result sets in their applications. Having a large query cache was just a big bandage for that.



                  There is a bigger reason that foreshadowed the demise of the query cache. Four years ago, I answered the post Why query_cache_type is disabled by default start from MySQL 5.6?. Is short, the query cache was always inspecting the InnoDB Buffer Pool for changes. You can find this on Pages 209-215 of High Performance MySQL (2nd Edition).



                  I mentioned this over the years:




                  • Sep 05, 2012 : Is the overhead of frequent query cache invalidation ever worth it?


                  • Sep 25, 2013 : invalidating query cache entries(key)


                  • Sep 26, 2013 : query cache hit value is not changing in my database


                  • Dec 23, 2013 : MySQL with high CPU and memory usage

                  RIP Query Cache !!!







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 3 hours ago









                  RolandoMySQLDBA

                  137k24215365




                  137k24215365






















                      up vote
                      1
                      down vote













                      There is a detailed blog from the MySQL server team about this, where Matt Lord says:




                      The query cache has been disabled-by-default since MySQL 5.6 (2013) as it is known to not scale with high-throughput workloads on multi-core machines.



                      We considered what improvements we could make to query cache versus optimizations that we could make which provide improvements to all workloads.



                      While these choices themselves are orthogonal, engineering resources are finite. That is to say that we are shifting strategy to invest in improvements that are more generally applicable to all workloads.







                      share|improve this answer


























                        up vote
                        1
                        down vote













                        There is a detailed blog from the MySQL server team about this, where Matt Lord says:




                        The query cache has been disabled-by-default since MySQL 5.6 (2013) as it is known to not scale with high-throughput workloads on multi-core machines.



                        We considered what improvements we could make to query cache versus optimizations that we could make which provide improvements to all workloads.



                        While these choices themselves are orthogonal, engineering resources are finite. That is to say that we are shifting strategy to invest in improvements that are more generally applicable to all workloads.







                        share|improve this answer
























                          up vote
                          1
                          down vote










                          up vote
                          1
                          down vote









                          There is a detailed blog from the MySQL server team about this, where Matt Lord says:




                          The query cache has been disabled-by-default since MySQL 5.6 (2013) as it is known to not scale with high-throughput workloads on multi-core machines.



                          We considered what improvements we could make to query cache versus optimizations that we could make which provide improvements to all workloads.



                          While these choices themselves are orthogonal, engineering resources are finite. That is to say that we are shifting strategy to invest in improvements that are more generally applicable to all workloads.







                          share|improve this answer














                          There is a detailed blog from the MySQL server team about this, where Matt Lord says:




                          The query cache has been disabled-by-default since MySQL 5.6 (2013) as it is known to not scale with high-throughput workloads on multi-core machines.



                          We considered what improvements we could make to query cache versus optimizations that we could make which provide improvements to all workloads.



                          While these choices themselves are orthogonal, engineering resources are finite. That is to say that we are shifting strategy to invest in improvements that are more generally applicable to all workloads.








                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited 1 hour ago









                          Paul White♦

                          46.6k14251399




                          46.6k14251399










                          answered 3 hours ago









                          danblack

                          4387




                          4387



























                               

                              draft saved


                              draft discarded















































                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f217577%2fwhy-mysql-remove-query-cache-in-8-0-version%23new-answer', 'question_page');

                              );

                              Post as a guest
































































                              Comments

                              Post a Comment

                              Popular posts from this blog

                              What does second last employer means? [closed]

                              Image
                              Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote -3 down vote favorite Say, for example I have worked in the following companies, Company A => 2010 - 2011 Company B => 2011 - 2012 Company C => 2012 - Till Date Company D => Have offer Now assume Company D is asking to submit documents from my second last employer. So from the list of companies given, which company would be qualified as second last employer? software-industry employer share | improve this question asked Aug 10 '14 at 5:16 Rajaprabhu Aravindasamy 559 1 6 13 closed as off-topic by Jim G., jmort253 ♦ Aug 11 '14 at 1:58 This question appears to be off-topic. The users who voted to close gave this specific reason: "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address...
                              Read more

                              Installing NextGIS Connect into QGIS 3?

                              Image
                              Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 1 down vote favorite Just acquired free version of NEXTGIS and trying to install the plugin for QGIS. It tells me it was not designed for version 3 of QGIS. How do I set up the QGIS-NEXTGIS interface then? qgis qgis-plugins nextgis share | improve this question edited 3 hours ago PolyGeo ♦ 51.9k 17 77 233 asked 4 hours ago IanGS 16 4 New contributor IanGS is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  up vote 1 down vote favorite Just acquired free version of NEXTGIS and trying to install the plugin for QGIS. It tells me it was not designed for version 3 of QGIS. How do I set up the QGIS-NEXTGIS interface then? qgis qgis-plugin...
                              Read more

                              One-line joke

                              A one-liner is a joke that is delivered in a single line. A good one-liner is said to be pithy - concise and meaningful. [1] Comedians and actors use this comedic method as part of their act, e.g. Jimmy Carr, Tommy Cooper, Rodney Dangerfield, Norm Macdonald, Ken Dodd, Stewart Francis, Zach Galifianakis, Mitch Hedberg, Anthony Jeselnik, Milton Jones, Shappi Khorsandi, Jay London, Mark Linn-Baker, Demetri Martin, Groucho Marx, Dan Mintz, Emo Philips, Tim Vine, Steven Wright and Henny Youngman and Arnold Schwarzenegger. [ citation needed ] Many fictional characters are also known to deliver one-liners, including James Bond, who usually includes pithy and laconic quips after disposing of a villain. [ citation needed ] Examples "A baby seal walks into a club." "A dyslexic man walks into a bra." (Anonymous) "There are three types of people, those who can count and those who can't." "Venison's dear, isn't it?" (Jimmy Carr) "An escala...
                              Read more