[Solved] How to improve the performace of Left Join Inner Join sql ( mysql)

How to optimize this SQL query?

In case you have your own slow SQL query, you can optimize it automatically here.

For the query above, the following recommendations will be helpful as part of the SQL tuning process.
You'll find 3 sections below:

  1. Description of the steps you can take to speed up the query.
  2. The optimal indexes for this query, which you can copy and create in your database.
  3. An automatically re-written query you can copy and execute in your database.
The optimization process and recommendations:
  1. Avoid LIKE Searches With Leading Wildcard (query line: 14): The database will not use an index when using like searches with a leading wildcard (e.g. '%funny%'). Although it's not always a satisfactory solution, please consider using prefix-match LIKE patterns (e.g. 'TERM%').
  2. Avoid OFFSET In LIMIT Clause (query line: 19): OFFSET clauses can be very slow when used with high offsets (e.g. with high page numbers when implementing paging). Instead, use the following \u003ca target\u003d"_blank" href\u003d"http://www.eversql.com/faster-pagination-in-mysql-why-order-by-with-limit-and-offset-is-slow/"\u003eseek method\u003c/a\u003e, which provides better and more stable response rates.
  3. Avoid Selecting Unnecessary Columns (query line: 2): Avoid selecting all columns with the '*' wildcard, unless you intend to use them all. Selecting redundant columns may result in unnecessary performance degradation.
  4. Prefer Direct Join Over Joined Subquery (query line: 13): We advise against using subqueries as they are not optimized well by the optimizer. Therefore, we recommend to replace subqueries with JOIN clauses.
  5. Use Numeric Column Types For Numeric Values (query line: 16): Referencing a numeric value (e.g. 1318949954) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
  6. Use Numeric Column Types For Numeric Values (query line: 17): Referencing a numeric value (e.g. 1) as a string in a WHERE clause might result in poor performance. Possible impacts of storing numbers as varchars: more space will be used, you won't be able to perform arithmetic operations, the data won't be self-validated, aggregation functions like SUM won't work, the output may sort incorrectly and more. If the column is numeric, remove the quotes from the constant value, to make sure a numeric comparison is done.
The optimized query:
SELECT
        SQL_CACHE se_media.* 
    FROM
        se_media 
    LEFT JOIN
        se_albums 
            ON se_albums.album_id = se_media.media_album_id 
    LEFT JOIN
        se_users 
            ON se_albums.album_user_id = se_users.user_id 
    LEFT JOIN
        se_media AS tagobjects_1 
            ON se_media.media_id = tagobjects_1.media_id 
            AND tagobjects_1.media_title LIKE '%funny%' 
    WHERE
        media_date_created <= '1318949954' 
        AND media_search = '1' 
    ORDER BY
        media_date_created DESC LIMIT 0,
        10

Related Articles



* original question posted on StackOverflow here.