Speed up SUM() on a result with JOINS in MySQL












0















I have a query with a combination of 6 left joins and inner joins. The query gives a result of 25000 records in 112ms. When I do a SUM() the query takes 4s. A SUM() another table with 35000 records without joins take 100ms (without index) to execute. I am unable to understand why. I am using MySQL.










share|improve this question














bumped to the homepage by Community 12 mins ago


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
















  • The speed of an operation depends on the size of the tables overall, the internal structure of the data, and how the data needs to be organised/parsed. You can't expect a direct relationship between the number of records on a table and the time it takes an operation to complete. You'll need to provide the DDL of your tables, your queries, and an explain/analyze results to get any specific support.

    – Ziggy Crueltyfree Zeitgeister
    May 30 '16 at 1:26






  • 1





    Use EXPLAIN to get the query plans with and without the sum(), compare them and if you don't see a solution, add them to your question.

    – jkavalik
    May 30 '16 at 8:55
















0















I have a query with a combination of 6 left joins and inner joins. The query gives a result of 25000 records in 112ms. When I do a SUM() the query takes 4s. A SUM() another table with 35000 records without joins take 100ms (without index) to execute. I am unable to understand why. I am using MySQL.










share|improve this question














bumped to the homepage by Community 12 mins ago


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
















  • The speed of an operation depends on the size of the tables overall, the internal structure of the data, and how the data needs to be organised/parsed. You can't expect a direct relationship between the number of records on a table and the time it takes an operation to complete. You'll need to provide the DDL of your tables, your queries, and an explain/analyze results to get any specific support.

    – Ziggy Crueltyfree Zeitgeister
    May 30 '16 at 1:26






  • 1





    Use EXPLAIN to get the query plans with and without the sum(), compare them and if you don't see a solution, add them to your question.

    – jkavalik
    May 30 '16 at 8:55














0












0








0








I have a query with a combination of 6 left joins and inner joins. The query gives a result of 25000 records in 112ms. When I do a SUM() the query takes 4s. A SUM() another table with 35000 records without joins take 100ms (without index) to execute. I am unable to understand why. I am using MySQL.










share|improve this question














I have a query with a combination of 6 left joins and inner joins. The query gives a result of 25000 records in 112ms. When I do a SUM() the query takes 4s. A SUM() another table with 35000 records without joins take 100ms (without index) to execute. I am unable to understand why. I am using MySQL.







mysql join






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 29 '16 at 7:52









Jaseem AbbasJaseem Abbas

1183




1183





bumped to the homepage by Community 12 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 12 mins ago


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















  • The speed of an operation depends on the size of the tables overall, the internal structure of the data, and how the data needs to be organised/parsed. You can't expect a direct relationship between the number of records on a table and the time it takes an operation to complete. You'll need to provide the DDL of your tables, your queries, and an explain/analyze results to get any specific support.

    – Ziggy Crueltyfree Zeitgeister
    May 30 '16 at 1:26






  • 1





    Use EXPLAIN to get the query plans with and without the sum(), compare them and if you don't see a solution, add them to your question.

    – jkavalik
    May 30 '16 at 8:55



















  • The speed of an operation depends on the size of the tables overall, the internal structure of the data, and how the data needs to be organised/parsed. You can't expect a direct relationship between the number of records on a table and the time it takes an operation to complete. You'll need to provide the DDL of your tables, your queries, and an explain/analyze results to get any specific support.

    – Ziggy Crueltyfree Zeitgeister
    May 30 '16 at 1:26






  • 1





    Use EXPLAIN to get the query plans with and without the sum(), compare them and if you don't see a solution, add them to your question.

    – jkavalik
    May 30 '16 at 8:55

















The speed of an operation depends on the size of the tables overall, the internal structure of the data, and how the data needs to be organised/parsed. You can't expect a direct relationship between the number of records on a table and the time it takes an operation to complete. You'll need to provide the DDL of your tables, your queries, and an explain/analyze results to get any specific support.

– Ziggy Crueltyfree Zeitgeister
May 30 '16 at 1:26





The speed of an operation depends on the size of the tables overall, the internal structure of the data, and how the data needs to be organised/parsed. You can't expect a direct relationship between the number of records on a table and the time it takes an operation to complete. You'll need to provide the DDL of your tables, your queries, and an explain/analyze results to get any specific support.

– Ziggy Crueltyfree Zeitgeister
May 30 '16 at 1:26




1




1





Use EXPLAIN to get the query plans with and without the sum(), compare them and if you don't see a solution, add them to your question.

– jkavalik
May 30 '16 at 8:55





Use EXPLAIN to get the query plans with and without the sum(), compare them and if you don't see a solution, add them to your question.

– jkavalik
May 30 '16 at 8:55










1 Answer
1






active

oldest

votes


















0














SELECT SUM(...)
FROM ...
JOIN ...


usually computes an inflated value for SUM. This is because the JOIN inflates the number of rows over which SUM applies.



See if you can write something like



SELECT ( SELECT SUM(...) FROM ... WHERE ... )  -- a correlated subquery
FROM
...


If you want more discussion, show us your code.






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%2f139853%2fspeed-up-sum-on-a-result-with-joins-in-mysql%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














    SELECT SUM(...)
    FROM ...
    JOIN ...


    usually computes an inflated value for SUM. This is because the JOIN inflates the number of rows over which SUM applies.



    See if you can write something like



    SELECT ( SELECT SUM(...) FROM ... WHERE ... )  -- a correlated subquery
    FROM
    ...


    If you want more discussion, show us your code.






    share|improve this answer




























      0














      SELECT SUM(...)
      FROM ...
      JOIN ...


      usually computes an inflated value for SUM. This is because the JOIN inflates the number of rows over which SUM applies.



      See if you can write something like



      SELECT ( SELECT SUM(...) FROM ... WHERE ... )  -- a correlated subquery
      FROM
      ...


      If you want more discussion, show us your code.






      share|improve this answer


























        0












        0








        0







        SELECT SUM(...)
        FROM ...
        JOIN ...


        usually computes an inflated value for SUM. This is because the JOIN inflates the number of rows over which SUM applies.



        See if you can write something like



        SELECT ( SELECT SUM(...) FROM ... WHERE ... )  -- a correlated subquery
        FROM
        ...


        If you want more discussion, show us your code.






        share|improve this answer













        SELECT SUM(...)
        FROM ...
        JOIN ...


        usually computes an inflated value for SUM. This is because the JOIN inflates the number of rows over which SUM applies.



        See if you can write something like



        SELECT ( SELECT SUM(...) FROM ... WHERE ... )  -- a correlated subquery
        FROM
        ...


        If you want more discussion, show us your code.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 6 '16 at 4:57









        Rick JamesRick James

        42k22258




        42k22258






























            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%2f139853%2fspeed-up-sum-on-a-result-with-joins-in-mysql%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

            Liste der Baudenkmale in Friedland (Mecklenburg)

            Single-Malt-Whisky

            Czorneboh