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

                              Long meetings (6-7 hours a day): Being “babysat” by supervisor

                              Image
                              Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 31 down vote favorite 4 I hold a PhD in mechanical engineering with a 7 year background in self-guided, self-paced research including 2 years as a graduate level course instructor and a subject matter expert for various engineering projects in a university setting in the United States. For the last 10-11 months, I am working in a research industry in France where my task is to debug C++ spaghetti code written over a period of several years by my current supervisor. It is a team of 2: just I and my supervisor. Diurnally, I am posed with a "bug of the day" to get out of this C++ code. My supervisor generally gives me about 15-30 minutes to solve it and then accosts me about whether or not the task is completed and then rinses and repeats this until the end of the day. Off-late, my supervisor has been holding 6-7 hour long "meetin
                              Read more

                              Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

                              Image
                              Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite Many fantasy worlds have multiple humanoid species (elves, orcs, humans, etc) living in the same world, in addition to that, they often have the ability to interbreed. And I can't help but question their believability... fantasy-races reproduction interspecies-relations share | improve this question edited Aug 9 at 14:46 Michael Kjörling ♦ 21.1k 10 85 161 asked Aug 9 at 13:13 Chlodio 118 6 closed as unclear what you're asking by MichaelK, Gryphon, John, Vincent, Frostfyre Aug 9 at 15:25 Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question. 3 Stack Exchange exist to
                              Read more

                              Confectionery

                              Image
                              Prepared foods made with a lot of sugar or other cabohydrates "Sweetmeat" redirects here. For the racehorse, see Sweetmeat (horse). Not to be confused with Sweetbread. This Kransekake is a traditional Scandinavian baker's confection. Confectionery is the art of making confections , which are food items that are rich in sugar and carbohydrates. Exact definitions are difficult. [1] In general, though, confectionery is divided into two broad and somewhat overlapping categories, bakers' confections and sugar confections. [2] Bakers' confectionery, also called flour confections , includes principally sweet pastries, cakes, and similar baked goods. Sugar confectionery includes candies ( sweets in British English), candied nuts, chocolates, chewing gum, bubble gum, pastillage, and other confections that are made primarily of sugar. In some cases, chocolate confections (confections made of chocolate) are treated as a separate category, as are sugar-free versions of
                              Read more