我可以優化這種查詢嗎？

Question

我有這個疑問：

SELECT 
    s.last_spread, s.sd, s.mean, s.id 
    ,c.id_ticker, c.coef 
    ,t.ticker 
    ,p.last, p.price 

FROM (SELECT * FROM spreads WHERE spreads.id_check=1 LIMIT 100,500) as s 

    INNER JOIN coef as c 
     ON c.id_spread = s.id 

    INNER JOIN tickers AS t 
      ON t.id = c.id_ticker 

    LEFT JOIN (SELECT prices.id_ticker, MAX(prices.date) as last, prices.price FROM prices GROUP BY prices.id_ticker) AS p 
      ON p.id_ticker = t.id 

這些表的模式：

mysql> desc spreads; 
+-------------+---------+------+-----+---------+----------------+ 
| Field  | Type | Null | Key | Default | Extra   | 
+-------------+---------+------+-----+---------+----------------+ 
| id   | int(11) | NO | PRI | NULL | auto_increment | 
| id_check | int(11) | YES | MUL | NULL |    | 
| sd   | double | YES |  | NULL |    | 
| mean  | double | YES |  | NULL |    | 
| last_spread | double | YES |  | NULL |    | 
+-------------+---------+------+-----+---------+----------------+ 
5 rows in set (0.00 sec) 


mysql> desc coef; 
+-----------+---------+------+-----+---------+----------------+ 
| Field  | Type | Null | Key | Default | Extra   | 
+-----------+---------+------+-----+---------+----------------+ 
| id  | int(11) | NO | PRI | NULL | auto_increment | 
| id_spread | int(11) | YES | MUL | NULL |    | 
| id_ticker | int(11) | YES |  | NULL |    | 
| coef  | double | YES |  | NULL |    | 
| side  | double | YES |  | NULL |    | 
+-----------+---------+------+-----+---------+----------------+ 
5 rows in set (0.00 sec) 


mysql> desc tickers; 
+----------+------------------+------+-----+---------+----------------+ 
| Field | Type    | Null | Key | Default | Extra   | 
+----------+------------------+------+-----+---------+----------------+ 
| id  | int(10) unsigned | NO | PRI | NULL | auto_increment | 
| ticker | varchar(45)  | NO |  | NULL |    | 
| name  | varchar(150)  | NO |  | NULL |    | 
| category | varchar(150)  | NO |  | NULL |    | 
| issuer | varchar(150)  | NO |  | NULL |    | 
+----------+------------------+------+-----+---------+----------------+ 
5 rows in set (0.00 sec) 


mysql> desc prices; 
+-----------+------------------+------+-----+---------+----------------+ 
| Field  | Type    | Null | Key | Default | Extra   | 
+-----------+------------------+------+-----+---------+----------------+ 
| id  | int(10) unsigned | NO | PRI | NULL | auto_increment | 
| id_ticker | int(10) unsigned | NO | MUL | NULL |    | 
| date  | date    | NO |  | NULL |    | 
| price  | double   | NO |  | NULL |    | 
+-----------+------------------+------+-----+---------+----------------+ 
4 rows in set (0.01 sec) 

這些是上述表的索引;

mysql> show indexes from spreads; 
+---------+------------+-----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | 
+---------+------------+-----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| spreads |   0 | PRIMARY |   1 | id   | A   |  2299 |  NULL | NULL |  | BTREE  |   | 
| spreads |   1 | check_idx |   1 | id_check | A   |   1 |  NULL | NULL | YES | BTREE  |   | 
+---------+------------+-----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
2 rows in set (0.00 sec) 


mysql> show indexes from coef; 
+-------+------------+-------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| Table | Non_unique | Key_name   | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | 
+-------+------------+-------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| coef |   0 | PRIMARY   |   1 | id   | A   |  9078 |  NULL | NULL |  | BTREE  |   | 
| coef |   1 | spread_ticker_idx |   1 | id_spread | A   |  NULL |  NULL | NULL | YES | BTREE  |   | 
| coef |   1 | spread_ticker_idx |   2 | id_ticker | A   |  NULL |  NULL | NULL | YES | BTREE  |   | 
+-------+------------+-------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
3 rows in set (0.00 sec) 


mysql> show indexes from tickers; 
+---------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | 
+---------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| tickers |   0 | PRIMARY |   1 | id   | A   |   100 |  NULL | NULL |  | BTREE  |   | 
+---------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
1 row in set (0.00 sec) 


mysql> show indexes from prices; 
+--------+------------+-----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | 
+--------+------------+-----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
| prices |   0 | PRIMARY |   1 | id   | A   |  19962 |  NULL | NULL |  | BTREE  |   | 
| prices |   1 | id_ticker |   1 | id_ticker | A   |  19962 |  NULL | NULL |  | BTREE  |   | 
+--------+------------+-----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+ 
2 rows in set (0.15 sec) 

，這是查詢的解釋：

+----+-------------+------------+--------+-------------------+-------------------+---------+---------------------------+--------+-------------+ 
| id | select_type | table  | type | possible_keys  | key    | key_len | ref      | rows | Extra  | 
+----+-------------+------------+--------+-------------------+-------------------+---------+---------------------------+--------+-------------+ 
| 1 | PRIMARY  | <derived2> | ALL | NULL    | NULL    | NULL | NULL      | 500 |    | 
| 1 | PRIMARY  | c   | ref | spread_ticker_idx | spread_ticker_idx | 5  | s.id      |  90 | Using where | 
| 1 | PRIMARY  | t   | eq_ref | PRIMARY   | PRIMARY   | 4  | spreadtrading.c.id_ticker |  1 | Using where | 
| 1 | PRIMARY  | <derived3> | ALL | NULL    | NULL    | NULL | NULL      | 100 |    | 
| 3 | DERIVED  | prices  | index | NULL    | id_ticker   | 4  | NULL      | 119774 |    | 
| 2 | DERIVED  | spreads | ref | check_idx   | check_idx   | 5  |       | 2298 | Using where | 
+----+-------------+------------+--------+-------------------+-------------------+---------+---------------------------+--------+-------------+ 
6 rows in set (0.27 sec) 

我能優化呢？

謝謝！

編輯：

我想知道，如果索引和表的結構是爲我上面貼的查詢優化。我使用這個查詢的結果是好的，它運行良好，但也許我可以優化它以增加查詢的「速度」。

Answer 1

我想你可能會通過刪除spreads子查詢並將WHERE子句移動到最後獲得一些結果，如下面的代碼所示。這會損失您的LIMIT限制 - 也許您可以在最後加上LIMIT子句，具體取決於您在限制輸出大小方面嘗試達到的目標。

SELECT 
    s.last_spread, s.sd, s.mean, s.id 
    ,c.id_ticker, c.coef 
    ,t.ticker 
    ,p.last, p.price 

FROM spreads as s 

    INNER JOIN coef as c 
     ON c.id_spread = s.id 

    INNER JOIN tickers AS t 
      ON t.id = c.id_ticker 

    LEFT JOIN (SELECT prices.id_ticker, MAX(prices.date) as last, prices.price FROM prices GROUP BY prices.id_ticker) AS p 
      ON p.id_ticker = t.id 
WHERE s.id_check = 1