此 SELECT 查询需要 180 秒才能完成
更新:
只是在更明显的地方提到它。当我将 IN 更改为 = 时,查询执行时间从 180 秒减少到 0.00008 秒。可笑的速度差异。
此 SQL 查询需要 180 秒才能完成!这怎么可能?有没有办法优化得更快?
SELECT IdLawVersionValidFrom
FROM question_law_version
WHERE IdQuestionLawVersion IN
(
SELECT MAX(IdQuestionLawVersion)
FROM question_law_version
WHERE IdQuestionLaw IN
(
SELECT MIN(IdQuestionLaw)
FROM question_law
WHERE IdQuestion=236 AND IdQuestionLaw>63
)
)
每个表中只有大约 5000 行,所以它不应该这么慢。
UPDATE:
Just to mention it on a more visible place. When I changed IN for =, the query execution time went from 180 down to 0.00008 seconds. Ridiculous speed difference.
This SQL query takes 180 seconds to finish! How is that possible? is there a way to optimize it to be faster?
SELECT IdLawVersionValidFrom
FROM question_law_version
WHERE IdQuestionLawVersion IN
(
SELECT MAX(IdQuestionLawVersion)
FROM question_law_version
WHERE IdQuestionLaw IN
(
SELECT MIN(IdQuestionLaw)
FROM question_law
WHERE IdQuestion=236 AND IdQuestionLaw>63
)
)
There are only about 5000 rows in each table so it shouldn't be so slow.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
(将我的评论作为答案发布,因为显然它确实有所作为!)
如果有人想进一步调查这一点,我刚刚做了一个测试,发现它很容易重现。
创建表
创建过程
填充表
查询 1
Equals 解释输出 http://img689.imageshack.us/img689/5592/equals .png
查询2(同样的问题)
在解释输出中http://img291.imageshack.us/img291 /8129/52037513.png
(Posting my comment as an answer as apparently it did make a difference!)
If anyone wants to investigate this further I've just done a test and found it very easy to reproduce.
Create Table
Create Procedure
Populate Table
Query 1
Equals Explain Output http://img689.imageshack.us/img689/5592/equals.png
Query 2 (same problem)
In Explain Output http://img291.imageshack.us/img291/8129/52037513.png
这里有一个很好的解释为什么 = 是比 IN 更好
Mysql 在内部查询方面存在问题 - 不能很好地使用索引(如果有的话)。
:
Here is a good explanation why = is better than IN
Mysql has problems with inner queries - not well using indexes (if at all).
Anyway:
您可以使用
EXPLAIN
找出查询执行速度如此之慢的原因。MySQL 并不真正喜欢嵌套子选择,所以可能发生的情况是它在磁盘上进行排序以获得最小值和最大值,但无法重用结果。
重写为连接可能会有所帮助。
如果只是寻找快速修复方法,请尝试:
You can use
EXPLAIN
to find out how is it possible for a query to execute so slow.MySQL does not really like nested subselects so probably what happens is that it goes and does sorts on disk to get min and max and fail to reuse results.
Rewriting as joins would probably help it.
If just looking for a quick fix try: