SHOW INNODB STATUS averages calculatedFrequently slow queries while in the 'Update' stateMysql DB server hits...

How should I ship cards?

What are Holorydmachines?

Badly designed reimbursement form. What does that say about the company?

What is the correct interpretation of the Gambling Results table in Xanathar's Guide to Everything?

Why Third 'Reich'? Why is 'reich' not translated when 'third' is? What is the English synonym of reich?

Does the kobold player race feature, Pack Tactics, give ranged attacks advantage?

Rudeness by being polite

Sing Baby Shark

Why would you use 2 alternate layout buttons instead of 1, when only one can be selected at once

A semicolon (';') is not needed after a function declaration. C++

Do error bars on probabilities have any meaning?

Is layered encryption more secure than long passwords?

Define function that behaves almost identically to Mathematica function

thispagestyle has no effect if no page broken(clearpage, newpage) is given

The Late Queen Gives in to Remorse - Reverse Hangman

Can I legally make a website about boycotting a certain company?

Getting size of dynamic C-style array vs. use of delete[]. Contradiction?

Is my plan for an air admittance valve ok?

Can I reorder the coordinates of a line when importing into QGIS a WKT linestring?

How do I ask to leave because of weather?

Taking an academic pseudonym?

Is it ethical to apply for a job on someone's behalf?

How do I write a maintainable, fast, compile-time bit-mask in C++?

Short Story - Man lives in isolation in a compound, plays tennis against a robot, arranges meeting with a woman



SHOW INNODB STATUS averages calculated


Frequently slow queries while in the 'Update' stateMysql DB server hits 400% CPUSHOW TABLE STATUS very slow on InnoDBOptimizing indexespoor and/or unreliable InnoDB performanceMySQL performance issue - intermittently slow queriesLarge No of MySQL running threads killing response timesSHOW ENGINE INNODB STATUS - SEMAPHORESInnodb: after 48 hours of optimizing 10mb/sec write speedExtreme performance loss due to moving from Mysql 5.7.23 to Mysql 8.0 (status, config included)













0















I am reading to all tutorials/books that when running SHOW ENGINE INNODB STATUS the Per second averages calculated from the last X sec, the X should be 20 to 30 seconds. I have never manage to exceed 10 sec, so my question is: Is the output valid? i can count on these statistics? Is there something i am missing here some parameter to collect status statistics more efficient?










share|improve this question














bumped to the homepage by Community 6 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I am reading to all tutorials/books that when running SHOW ENGINE INNODB STATUS the Per second averages calculated from the last X sec, the X should be 20 to 30 seconds. I have never manage to exceed 10 sec, so my question is: Is the output valid? i can count on these statistics? Is there something i am missing here some parameter to collect status statistics more efficient?










    share|improve this question














    bumped to the homepage by Community 6 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I am reading to all tutorials/books that when running SHOW ENGINE INNODB STATUS the Per second averages calculated from the last X sec, the X should be 20 to 30 seconds. I have never manage to exceed 10 sec, so my question is: Is the output valid? i can count on these statistics? Is there something i am missing here some parameter to collect status statistics more efficient?










      share|improve this question














      I am reading to all tutorials/books that when running SHOW ENGINE INNODB STATUS the Per second averages calculated from the last X sec, the X should be 20 to 30 seconds. I have never manage to exceed 10 sec, so my question is: Is the output valid? i can count on these statistics? Is there something i am missing here some parameter to collect status statistics more efficient?







      mysql innodb






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jul 4 '14 at 14:04









      AntoniosAntonios

      1,057413




      1,057413





      bumped to the homepage by Community 6 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 6 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The SHOW ENGINE INNODB STATUS G command will show data from the last time the command was run till now - not sure what it will be the first time. I can't shut down the server here, but if you run the command rapidly twice in succession, you'll see the time since last run - set your



          mysql> pager less;

          mysql> show engine innodb status G


          =====================================
          2014-07-04 15:44:42 7f0a2d9c9700 INNODB MONITOR OUTPUT
          =====================================
          Per second averages calculated from the last 6 seconds


          Take a look here - averages of less than ~30 seconds are worthless
          according to Peter Zaitsev. You could also take a look at Baron Schwartz's
          innotop tool - available here.






          share|improve this answer
























          • Thanks, but what does that mean the last time the command was run till now?

            – Antonios
            Jul 4 '14 at 15:00











          • Sorry if I wasn't clear. If you notice in my answer, I ran the SHOW ENGINE INNODB STATUS twice - the first time was 6 seconds before the example I showed you. As you have read, you should take averages over a longer period - I was just demonstrating the time that the command uses - you control it - if you issue the command twice, once immediately after the other, it will show 1 - 2 seconds.

            – Vérace
            Jul 4 '14 at 15:06













          • So if you have never run it before, it will give you the server up-time as average?

            – Antonios
            Jul 4 '14 at 15:09











          • That's what I said I wasn't sure of. You'll have to check that yourself, since I can't shutdown my server here.

            – Vérace
            Jul 4 '14 at 15:13











          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',
          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%2fdba.stackexchange.com%2fquestions%2f69732%2fshow-innodb-status-averages-calculated%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









          0














          The SHOW ENGINE INNODB STATUS G command will show data from the last time the command was run till now - not sure what it will be the first time. I can't shut down the server here, but if you run the command rapidly twice in succession, you'll see the time since last run - set your



          mysql> pager less;

          mysql> show engine innodb status G


          =====================================
          2014-07-04 15:44:42 7f0a2d9c9700 INNODB MONITOR OUTPUT
          =====================================
          Per second averages calculated from the last 6 seconds


          Take a look here - averages of less than ~30 seconds are worthless
          according to Peter Zaitsev. You could also take a look at Baron Schwartz's
          innotop tool - available here.






          share|improve this answer
























          • Thanks, but what does that mean the last time the command was run till now?

            – Antonios
            Jul 4 '14 at 15:00











          • Sorry if I wasn't clear. If you notice in my answer, I ran the SHOW ENGINE INNODB STATUS twice - the first time was 6 seconds before the example I showed you. As you have read, you should take averages over a longer period - I was just demonstrating the time that the command uses - you control it - if you issue the command twice, once immediately after the other, it will show 1 - 2 seconds.

            – Vérace
            Jul 4 '14 at 15:06













          • So if you have never run it before, it will give you the server up-time as average?

            – Antonios
            Jul 4 '14 at 15:09











          • That's what I said I wasn't sure of. You'll have to check that yourself, since I can't shutdown my server here.

            – Vérace
            Jul 4 '14 at 15:13
















          0














          The SHOW ENGINE INNODB STATUS G command will show data from the last time the command was run till now - not sure what it will be the first time. I can't shut down the server here, but if you run the command rapidly twice in succession, you'll see the time since last run - set your



          mysql> pager less;

          mysql> show engine innodb status G


          =====================================
          2014-07-04 15:44:42 7f0a2d9c9700 INNODB MONITOR OUTPUT
          =====================================
          Per second averages calculated from the last 6 seconds


          Take a look here - averages of less than ~30 seconds are worthless
          according to Peter Zaitsev. You could also take a look at Baron Schwartz's
          innotop tool - available here.






          share|improve this answer
























          • Thanks, but what does that mean the last time the command was run till now?

            – Antonios
            Jul 4 '14 at 15:00











          • Sorry if I wasn't clear. If you notice in my answer, I ran the SHOW ENGINE INNODB STATUS twice - the first time was 6 seconds before the example I showed you. As you have read, you should take averages over a longer period - I was just demonstrating the time that the command uses - you control it - if you issue the command twice, once immediately after the other, it will show 1 - 2 seconds.

            – Vérace
            Jul 4 '14 at 15:06













          • So if you have never run it before, it will give you the server up-time as average?

            – Antonios
            Jul 4 '14 at 15:09











          • That's what I said I wasn't sure of. You'll have to check that yourself, since I can't shutdown my server here.

            – Vérace
            Jul 4 '14 at 15:13














          0












          0








          0







          The SHOW ENGINE INNODB STATUS G command will show data from the last time the command was run till now - not sure what it will be the first time. I can't shut down the server here, but if you run the command rapidly twice in succession, you'll see the time since last run - set your



          mysql> pager less;

          mysql> show engine innodb status G


          =====================================
          2014-07-04 15:44:42 7f0a2d9c9700 INNODB MONITOR OUTPUT
          =====================================
          Per second averages calculated from the last 6 seconds


          Take a look here - averages of less than ~30 seconds are worthless
          according to Peter Zaitsev. You could also take a look at Baron Schwartz's
          innotop tool - available here.






          share|improve this answer













          The SHOW ENGINE INNODB STATUS G command will show data from the last time the command was run till now - not sure what it will be the first time. I can't shut down the server here, but if you run the command rapidly twice in succession, you'll see the time since last run - set your



          mysql> pager less;

          mysql> show engine innodb status G


          =====================================
          2014-07-04 15:44:42 7f0a2d9c9700 INNODB MONITOR OUTPUT
          =====================================
          Per second averages calculated from the last 6 seconds


          Take a look here - averages of less than ~30 seconds are worthless
          according to Peter Zaitsev. You could also take a look at Baron Schwartz's
          innotop tool - available here.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 4 '14 at 14:49









          VéraceVérace

          16.1k33550




          16.1k33550













          • Thanks, but what does that mean the last time the command was run till now?

            – Antonios
            Jul 4 '14 at 15:00











          • Sorry if I wasn't clear. If you notice in my answer, I ran the SHOW ENGINE INNODB STATUS twice - the first time was 6 seconds before the example I showed you. As you have read, you should take averages over a longer period - I was just demonstrating the time that the command uses - you control it - if you issue the command twice, once immediately after the other, it will show 1 - 2 seconds.

            – Vérace
            Jul 4 '14 at 15:06













          • So if you have never run it before, it will give you the server up-time as average?

            – Antonios
            Jul 4 '14 at 15:09











          • That's what I said I wasn't sure of. You'll have to check that yourself, since I can't shutdown my server here.

            – Vérace
            Jul 4 '14 at 15:13



















          • Thanks, but what does that mean the last time the command was run till now?

            – Antonios
            Jul 4 '14 at 15:00











          • Sorry if I wasn't clear. If you notice in my answer, I ran the SHOW ENGINE INNODB STATUS twice - the first time was 6 seconds before the example I showed you. As you have read, you should take averages over a longer period - I was just demonstrating the time that the command uses - you control it - if you issue the command twice, once immediately after the other, it will show 1 - 2 seconds.

            – Vérace
            Jul 4 '14 at 15:06













          • So if you have never run it before, it will give you the server up-time as average?

            – Antonios
            Jul 4 '14 at 15:09











          • That's what I said I wasn't sure of. You'll have to check that yourself, since I can't shutdown my server here.

            – Vérace
            Jul 4 '14 at 15:13

















          Thanks, but what does that mean the last time the command was run till now?

          – Antonios
          Jul 4 '14 at 15:00





          Thanks, but what does that mean the last time the command was run till now?

          – Antonios
          Jul 4 '14 at 15:00













          Sorry if I wasn't clear. If you notice in my answer, I ran the SHOW ENGINE INNODB STATUS twice - the first time was 6 seconds before the example I showed you. As you have read, you should take averages over a longer period - I was just demonstrating the time that the command uses - you control it - if you issue the command twice, once immediately after the other, it will show 1 - 2 seconds.

          – Vérace
          Jul 4 '14 at 15:06







          Sorry if I wasn't clear. If you notice in my answer, I ran the SHOW ENGINE INNODB STATUS twice - the first time was 6 seconds before the example I showed you. As you have read, you should take averages over a longer period - I was just demonstrating the time that the command uses - you control it - if you issue the command twice, once immediately after the other, it will show 1 - 2 seconds.

          – Vérace
          Jul 4 '14 at 15:06















          So if you have never run it before, it will give you the server up-time as average?

          – Antonios
          Jul 4 '14 at 15:09





          So if you have never run it before, it will give you the server up-time as average?

          – Antonios
          Jul 4 '14 at 15:09













          That's what I said I wasn't sure of. You'll have to check that yourself, since I can't shutdown my server here.

          – Vérace
          Jul 4 '14 at 15:13





          That's what I said I wasn't sure of. You'll have to check that yourself, since I can't shutdown my server here.

          – Vérace
          Jul 4 '14 at 15:13


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Database Administrators 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%2fdba.stackexchange.com%2fquestions%2f69732%2fshow-innodb-status-averages-calculated%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

          ORA-01691 (unable to extend lob segment) even though my tablespace has AUTOEXTEND onORA-01692: unable to...

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          Circunscripción electoral de Guipúzcoa Referencias Menú de navegaciónLas claves del sistema electoral en...