Very slow queries selecting @@ session variables. The Next CEO of Stack OverflowMySQL: 2...

Is it my responsibility to learn a new technology in my own time my employer wants to implement?

Solution of this Diophantine Equation

Trouble understanding the speech of overseas colleagues

What is the difference between "behavior" and "behaviour"?

Should I tutor a student who I know has cheated on their homework?

Text adventure game code

What's the point of interval inversion?

Unreliable Magic - Is it worth it?

'Given that' in a matrix

Was a professor correct to chastise me for writing "Prof. X" rather than "Professor X"?

Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?

What does "Its cash flow is deeply negative" mean?

What is meant by a M next to a roman numeral?

Why didn't Khan get resurrected in the Genesis Explosion?

When airplanes disconnect from a tanker during air to air refueling, why do they bank so sharply to the right?

Apart from "berlinern", do any other German dialects have a corresponding verb?

Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?

Why here is plural "We went to the movies last night."

WOW air has ceased operation, can I get my tickets refunded?

Customer Requests (Sometimes) Drive Me Bonkers!

Rotate a column

How to use tikz in fbox?

How long to clear the 'suck zone' of a turbofan after start is initiated?

Only print output after finding pattern



Very slow queries selecting @@ session variables.



The Next CEO of Stack OverflowMySQL: 2 separate queries run very fast, combined query with OR runs very slowVery Slow MySQL Queries, even with indexesIs it possible to optimize this query? Or any recommendations to speed it up?Double subquery is very slow, but independently they are finetwo similar queries with different results (one very slow)Very slow MySQL performanceVery Slow QueryVery light queries are in slow-query-log ! Why?Periodically very slow execution of simplest queriesslow queries on indexed columns (large datasets)












0















We're running locally managed databases for our Atlassian suite (Jira/Confluence/Fisheye). I noticed something strange in the slow query logs. There are a bunch of selects of session variables showing up like



# Schema: fisheyedb  Last_errno: 0  Killed: 0
# Query_time: 2.487396 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0
# Bytes_sent: 90 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
# QC_Hit: No Full_scan: No Full_join: No Tmp_table: No Tmp_table_on_disk: No
# Filesort: No Filesort_on_disk: No Merge_passes: 0
# No InnoDB statistics available for this query
use fisheyedb;
SET timestamp=1511794875;
SELECT @@session.tx_isolation;


We have the slow query time threshold set to 2 seconds.



They're so prevelant that they're the number 1 entry in our daily pt-query -digest archives



# Query 1: 0.08 QPS, 0.22x concurrency, ID 0x30AAEC10BC3D0C37 at byte 7953939
# This item is included in the report because it matches --limit.
# Scores: V/M = 0.33
# Time range: 2017-11-27 09:01:15 to 2017-11-28 00:11:48
# Attribute pct total min max avg 95% stddev median
# ============ === ======= ======= ======= ======= ======= ======= =======
# Count 25 4120
# Exec time 19 11926s 2s 14s 3s 5s 972ms 3s
# Lock time 0 0 0 0 0 0 0 0
# Rows sent 0 4.02k 1 1 1 1 0 1
# Rows examine 0 0 0 0 0 0 0 0
# Rows affecte 0 0 0 0 0 0 0 0
# Bytes sent 0 362.12k 90 91 90.00 88.31 0 88.31
# Merge passes 0 0 0 0 0 0 0 0
# Tmp tables 0 0 0 0 0 0 0 0
# Tmp disk tbl 0 0 0 0 0 0 0 0
# Tmp tbl size 0 0 0 0 0 0 0 0
# Query size 2 116.68k 29 29 29 29 0 29
# String:
# Databases fisheyedb (4105/99%), confluence... (15/0%)
# Hosts x.x.x.x
# Last errno 0
# Users fisheyeuse... (4105/99%), confluence... (15/0%)
# Query_time distribution
# 1us
# 10us
# 100us
# 1ms
# 10ms
# 100ms
# 1s ################################################################
# 10s+ #
# EXPLAIN /*!50100 PARTITIONS*/
SELECT @@session.tx_isolationG


What can cause reading a simple session variable like tx_isolation to be anything less than instantaneous?










share|improve this question
















bumped to the homepage by Community 8 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















    We're running locally managed databases for our Atlassian suite (Jira/Confluence/Fisheye). I noticed something strange in the slow query logs. There are a bunch of selects of session variables showing up like



    # Schema: fisheyedb  Last_errno: 0  Killed: 0
    # Query_time: 2.487396 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0
    # Bytes_sent: 90 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
    # QC_Hit: No Full_scan: No Full_join: No Tmp_table: No Tmp_table_on_disk: No
    # Filesort: No Filesort_on_disk: No Merge_passes: 0
    # No InnoDB statistics available for this query
    use fisheyedb;
    SET timestamp=1511794875;
    SELECT @@session.tx_isolation;


    We have the slow query time threshold set to 2 seconds.



    They're so prevelant that they're the number 1 entry in our daily pt-query -digest archives



    # Query 1: 0.08 QPS, 0.22x concurrency, ID 0x30AAEC10BC3D0C37 at byte 7953939
    # This item is included in the report because it matches --limit.
    # Scores: V/M = 0.33
    # Time range: 2017-11-27 09:01:15 to 2017-11-28 00:11:48
    # Attribute pct total min max avg 95% stddev median
    # ============ === ======= ======= ======= ======= ======= ======= =======
    # Count 25 4120
    # Exec time 19 11926s 2s 14s 3s 5s 972ms 3s
    # Lock time 0 0 0 0 0 0 0 0
    # Rows sent 0 4.02k 1 1 1 1 0 1
    # Rows examine 0 0 0 0 0 0 0 0
    # Rows affecte 0 0 0 0 0 0 0 0
    # Bytes sent 0 362.12k 90 91 90.00 88.31 0 88.31
    # Merge passes 0 0 0 0 0 0 0 0
    # Tmp tables 0 0 0 0 0 0 0 0
    # Tmp disk tbl 0 0 0 0 0 0 0 0
    # Tmp tbl size 0 0 0 0 0 0 0 0
    # Query size 2 116.68k 29 29 29 29 0 29
    # String:
    # Databases fisheyedb (4105/99%), confluence... (15/0%)
    # Hosts x.x.x.x
    # Last errno 0
    # Users fisheyeuse... (4105/99%), confluence... (15/0%)
    # Query_time distribution
    # 1us
    # 10us
    # 100us
    # 1ms
    # 10ms
    # 100ms
    # 1s ################################################################
    # 10s+ #
    # EXPLAIN /*!50100 PARTITIONS*/
    SELECT @@session.tx_isolationG


    What can cause reading a simple session variable like tx_isolation to be anything less than instantaneous?










    share|improve this question
















    bumped to the homepage by Community 8 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








      We're running locally managed databases for our Atlassian suite (Jira/Confluence/Fisheye). I noticed something strange in the slow query logs. There are a bunch of selects of session variables showing up like



      # Schema: fisheyedb  Last_errno: 0  Killed: 0
      # Query_time: 2.487396 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0
      # Bytes_sent: 90 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
      # QC_Hit: No Full_scan: No Full_join: No Tmp_table: No Tmp_table_on_disk: No
      # Filesort: No Filesort_on_disk: No Merge_passes: 0
      # No InnoDB statistics available for this query
      use fisheyedb;
      SET timestamp=1511794875;
      SELECT @@session.tx_isolation;


      We have the slow query time threshold set to 2 seconds.



      They're so prevelant that they're the number 1 entry in our daily pt-query -digest archives



      # Query 1: 0.08 QPS, 0.22x concurrency, ID 0x30AAEC10BC3D0C37 at byte 7953939
      # This item is included in the report because it matches --limit.
      # Scores: V/M = 0.33
      # Time range: 2017-11-27 09:01:15 to 2017-11-28 00:11:48
      # Attribute pct total min max avg 95% stddev median
      # ============ === ======= ======= ======= ======= ======= ======= =======
      # Count 25 4120
      # Exec time 19 11926s 2s 14s 3s 5s 972ms 3s
      # Lock time 0 0 0 0 0 0 0 0
      # Rows sent 0 4.02k 1 1 1 1 0 1
      # Rows examine 0 0 0 0 0 0 0 0
      # Rows affecte 0 0 0 0 0 0 0 0
      # Bytes sent 0 362.12k 90 91 90.00 88.31 0 88.31
      # Merge passes 0 0 0 0 0 0 0 0
      # Tmp tables 0 0 0 0 0 0 0 0
      # Tmp disk tbl 0 0 0 0 0 0 0 0
      # Tmp tbl size 0 0 0 0 0 0 0 0
      # Query size 2 116.68k 29 29 29 29 0 29
      # String:
      # Databases fisheyedb (4105/99%), confluence... (15/0%)
      # Hosts x.x.x.x
      # Last errno 0
      # Users fisheyeuse... (4105/99%), confluence... (15/0%)
      # Query_time distribution
      # 1us
      # 10us
      # 100us
      # 1ms
      # 10ms
      # 100ms
      # 1s ################################################################
      # 10s+ #
      # EXPLAIN /*!50100 PARTITIONS*/
      SELECT @@session.tx_isolationG


      What can cause reading a simple session variable like tx_isolation to be anything less than instantaneous?










      share|improve this question
















      We're running locally managed databases for our Atlassian suite (Jira/Confluence/Fisheye). I noticed something strange in the slow query logs. There are a bunch of selects of session variables showing up like



      # Schema: fisheyedb  Last_errno: 0  Killed: 0
      # Query_time: 2.487396 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 Rows_affected: 0
      # Bytes_sent: 90 Tmp_tables: 0 Tmp_disk_tables: 0 Tmp_table_sizes: 0
      # QC_Hit: No Full_scan: No Full_join: No Tmp_table: No Tmp_table_on_disk: No
      # Filesort: No Filesort_on_disk: No Merge_passes: 0
      # No InnoDB statistics available for this query
      use fisheyedb;
      SET timestamp=1511794875;
      SELECT @@session.tx_isolation;


      We have the slow query time threshold set to 2 seconds.



      They're so prevelant that they're the number 1 entry in our daily pt-query -digest archives



      # Query 1: 0.08 QPS, 0.22x concurrency, ID 0x30AAEC10BC3D0C37 at byte 7953939
      # This item is included in the report because it matches --limit.
      # Scores: V/M = 0.33
      # Time range: 2017-11-27 09:01:15 to 2017-11-28 00:11:48
      # Attribute pct total min max avg 95% stddev median
      # ============ === ======= ======= ======= ======= ======= ======= =======
      # Count 25 4120
      # Exec time 19 11926s 2s 14s 3s 5s 972ms 3s
      # Lock time 0 0 0 0 0 0 0 0
      # Rows sent 0 4.02k 1 1 1 1 0 1
      # Rows examine 0 0 0 0 0 0 0 0
      # Rows affecte 0 0 0 0 0 0 0 0
      # Bytes sent 0 362.12k 90 91 90.00 88.31 0 88.31
      # Merge passes 0 0 0 0 0 0 0 0
      # Tmp tables 0 0 0 0 0 0 0 0
      # Tmp disk tbl 0 0 0 0 0 0 0 0
      # Tmp tbl size 0 0 0 0 0 0 0 0
      # Query size 2 116.68k 29 29 29 29 0 29
      # String:
      # Databases fisheyedb (4105/99%), confluence... (15/0%)
      # Hosts x.x.x.x
      # Last errno 0
      # Users fisheyeuse... (4105/99%), confluence... (15/0%)
      # Query_time distribution
      # 1us
      # 10us
      # 100us
      # 1ms
      # 10ms
      # 100ms
      # 1s ################################################################
      # 10s+ #
      # EXPLAIN /*!50100 PARTITIONS*/
      SELECT @@session.tx_isolationG


      What can cause reading a simple session variable like tx_isolation to be anything less than instantaneous?







      mysql atlassian






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 29 '17 at 0:46







      atxdba

















      asked Nov 28 '17 at 23:32









      atxdbaatxdba

      3,89842654




      3,89842654





      bumped to the homepage by Community 8 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 8 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















          • Sometimes things like this happen because of other things going on at the same time. Can you spot such in the slowlog?

          • The probably will probably be solved in version 8.0, when a number of things get turned into real InnoDB tables.

          • Some 3rd party products issue an awful number of seemingly spurious and redundant information queries. Let's see the output from SHOW GLOBAL STATUS LIKE 'Com%';

          • Set long_query_time = 0.1 and see if you catch a lot more of these queries, plus other things.






          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',
            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%2f191935%2fvery-slow-queries-selecting-session-variables%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















            • Sometimes things like this happen because of other things going on at the same time. Can you spot such in the slowlog?

            • The probably will probably be solved in version 8.0, when a number of things get turned into real InnoDB tables.

            • Some 3rd party products issue an awful number of seemingly spurious and redundant information queries. Let's see the output from SHOW GLOBAL STATUS LIKE 'Com%';

            • Set long_query_time = 0.1 and see if you catch a lot more of these queries, plus other things.






            share|improve this answer




























              0















              • Sometimes things like this happen because of other things going on at the same time. Can you spot such in the slowlog?

              • The probably will probably be solved in version 8.0, when a number of things get turned into real InnoDB tables.

              • Some 3rd party products issue an awful number of seemingly spurious and redundant information queries. Let's see the output from SHOW GLOBAL STATUS LIKE 'Com%';

              • Set long_query_time = 0.1 and see if you catch a lot more of these queries, plus other things.






              share|improve this answer


























                0












                0








                0








                • Sometimes things like this happen because of other things going on at the same time. Can you spot such in the slowlog?

                • The probably will probably be solved in version 8.0, when a number of things get turned into real InnoDB tables.

                • Some 3rd party products issue an awful number of seemingly spurious and redundant information queries. Let's see the output from SHOW GLOBAL STATUS LIKE 'Com%';

                • Set long_query_time = 0.1 and see if you catch a lot more of these queries, plus other things.






                share|improve this answer














                • Sometimes things like this happen because of other things going on at the same time. Can you spot such in the slowlog?

                • The probably will probably be solved in version 8.0, when a number of things get turned into real InnoDB tables.

                • Some 3rd party products issue an awful number of seemingly spurious and redundant information queries. Let's see the output from SHOW GLOBAL STATUS LIKE 'Com%';

                • Set long_query_time = 0.1 and see if you catch a lot more of these queries, plus other things.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 29 '17 at 1:03









                Rick JamesRick James

                43.7k22259




                43.7k22259






























                    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%2f191935%2fvery-slow-queries-selecting-session-variables%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

                    Parapolítica Índice Antecedentes El escándalo Proceso judicial Consecuencias Véase...

                    How to remove border from elements in the last row?Targeting flex items on the last rowHow to vertically wrap...

                    Tecnologías entrañables Índice Antecedentes Desarrollo Tecnologías Entrañables en la...