- mongodb - 在 MongoDB mapreduce 中,如何展平值对象?
- javascript - 对象传播与 Object.assign
- html - 输入类型 ="submit"Vs 按钮标签它们可以互换吗?
- sql - 使用 MongoDB 而不是 MS SQL Server 的优缺点
我有两张 table ; songs
有 48 959 281 行,popular_songs
有 5 721 117 行。
这是两个表的结构:
CREATE TABLE songs (
songId BIGINT(20) NOT NULL,
songName VARCHAR(1000) NOT NULL,
songDuration BIGINT(20) NOT NULL,
songPreview VARCHAR(1000) NOT NULL,
PRIMARY KEY (songId),
INDEX (songDuration)
)
ENGINE = InnoDB
DEFAULT CHARSET = utf8
DEFAULT COLLATE utf8_general_ci;
CREATE TABLE popular_songs (
storeFrontId BIGINT(20) NOT NULL,
genreId BIGINT(20) NOT NULL,
songId BIGINT(20) NOT NULL,
songRank INT(11) NOT NULL,
INDEX (storeFrontId),
INDEX (genreId),
INDEX (songId),
INDEX (songRank),
CONSTRAINT popular_song UNIQUE (storeFrontId, genreId, songId),
FOREIGN KEY (storeFrontId) REFERENCES storefront (storeFrontId),
FOREIGN KEY (genreId) REFERENCES genre (genreId),
FOREIGN KEY (songId) REFERENCES songs (songId)
)
ENGINE = InnoDB
DEFAULT CHARSET = utf8
DEFAULT COLLATE utf8_general_ci;
当我在下面运行这两个问题时,一切正常。
mysql> SELECT count(*) FROM songs;
+----------+
| count(*) |
+----------+
| 48959281 |
+----------+
1 row in set (9.10 sec)
mysql> SHOW PROFILE;
+--------------------------------+----------+
| Status | Duration |
+--------------------------------+----------+
| starting | 0.000008 |
| Waiting for query cache lock | 0.000002 |
| checking query cache for query | 0.000019 |
| checking permissions | 0.000003 |
| Opening tables | 0.000011 |
| System lock | 0.000004 |
| Waiting for query cache lock | 0.000017 |
| init | 0.000006 |
| optimizing | 0.000003 |
| statistics | 0.000004 |
| preparing | 0.000004 |
| executing | 0.000003 |
| Sending data | 9.100444 |
| end | 0.000012 |
| query end | 0.000005 |
| closing tables | 0.000008 |
| freeing items | 0.000007 |
| Waiting for query cache lock | 0.000002 |
| freeing items | 0.000012 |
| Waiting for query cache lock | 0.000002 |
| freeing items | 0.000001 |
| storing result in query cache | 0.000002 |
| logging slow query | 0.000001 |
| cleaning up | 0.000003 |
+--------------------------------+----------+
24 rows in set (0.00 sec)
mysql> SELECT count(*) FROM popular_songs;
+----------+
| count(*) |
+----------+
| 5721117 |
+----------+
1 row in set (1.34 sec)
mysql> SHOW PROFILE;
+--------------------------------+----------+
| Status | Duration |
+--------------------------------+----------+
| starting | 0.000012 |
| Waiting for query cache lock | 0.000004 |
| checking query cache for query | 0.000037 |
| checking permissions | 0.000006 |
| Opening tables | 0.000017 |
| System lock | 0.000007 |
| Waiting for query cache lock | 0.000031 |
| init | 0.000010 |
| optimizing | 0.000017 |
| statistics | 0.000004 |
| preparing | 0.000004 |
| executing | 0.000003 |
| Sending data | 1.343991 |
| end | 0.000010 |
| query end | 0.000005 |
| closing tables | 0.000007 |
| freeing items | 0.000007 |
| Waiting for query cache lock | 0.000002 |
| freeing items | 0.000011 |
| Waiting for query cache lock | 0.000001 |
| freeing items | 0.000001 |
| storing result in query cache | 0.000002 |
| logging slow query | 0.000001 |
| cleaning up | 0.000003 |
+--------------------------------+----------+
24 rows in set (0.00 sec)
当我运行以下这些查询时,MySQL 没有响应。我不明白这是什么原因。
SELECT COUNT(*)
FROM songs
INNER JOIN popular_songs ON popular_songs.songId = songs.songId
SELECT COUNT(*)
FROM songs
INNER JOIN popular_songs ON popular_songs.songId = songs.songId
WHERE songs.songDuration > 0
更新:
MySQL 响应了以上两个查询。但是 Sending data
需要 250-300 秒。如何对此进行优化。
EXPLAIN EXTENDED 报告:
mysql> EXPLAIN EXTENDED
-> SELECT COUNT(*)
-> FROM songs
-> INNER JOIN popular_songs ON popular_songs.songId = songs.songId;
+----+-------------+---------------+--------+---------------+----------+---------+-----------------------------+---------+----------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+---------------+--------+---------------+----------+---------+-----------------------------+---------+----------+-------------+
| 1 | SIMPLE | popular_songs | index | songId | songRank | 4 | NULL | 6449163 | 100.00 | Using index |
| 1 | SIMPLE | songs | eq_ref | PRIMARY | PRIMARY | 8 | itunes.popular_songs.songId | 1 | 100.00 | Using index |
+----+-------------+---------------+--------+---------------+----------+---------+-----------------------------+---------+----------+-------------+
2 rows in set, 1 warning (0.01 sec)
mysql> EXPLAIN EXTENDED
-> SELECT COUNT(*)
-> FROM songs
-> INNER JOIN popular_songs ON popular_songs.songId = songs.songId
-> WHERE songs.songDuration > 0;
+----+-------------+---------------+--------+----------------------+----------+---------+-----------------------------+---------+----------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+---------------+--------+----------------------+----------+---------+-----------------------------+---------+----------+-------------+
| 1 | SIMPLE | popular_songs | index | songId | songRank | 4 | NULL | 6449163 | 100.00 | Using index |
| 1 | SIMPLE | songs | eq_ref | PRIMARY,songDuration | PRIMARY | 8 | itunes.popular_songs.songId | 1 | 100.00 | Using where |
+----+-------------+---------------+--------+----------------------+----------+---------+-----------------------------+---------+----------+-------------+
2 rows in set, 1 warning (0.00 sec)
当使用 INDEX songId
连接两个表时:
mysql> SELECT COUNT(*) FROM songs INNER JOIN popular_songs USE INDEX FOR JOIN (songId) ON popular_songs.songId = songs.songId;
+----------+
| COUNT(*) |
+----------+
| 5721117 |
+----------+
1 row in set (25.35 sec)
mysql> SHOW PROFILE;
+--------------------------------+-----------+
| Status | Duration |
+--------------------------------+-----------+
| starting | 0.000011 |
| Waiting for query cache lock | 0.000004 |
| checking query cache for query | 0.000045 |
| checking permissions | 0.000004 |
| checking permissions | 0.000004 |
| Opening tables | 0.000023 |
| System lock | 0.000007 |
| Waiting for query cache lock | 0.000030 |
| init | 0.000021 |
| optimizing | 0.000011 |
| statistics | 0.000020 |
| preparing | 0.000012 |
| executing | 0.000005 |
| Sending data | 25.350160 |
| end | 0.000019 |
| query end | 0.000005 |
| closing tables | 0.000024 |
| freeing items | 0.000022 |
| Waiting for query cache lock | 0.000002 |
| freeing items | 0.000016 |
| Waiting for query cache lock | 0.000001 |
| freeing items | 0.000001 |
| storing result in query cache | 0.000002 |
| logging slow query | 0.000001 |
| logging slow query | 0.000005 |
| cleaning up | 0.000003 |
+--------------------------------+-----------+
26 rows in set (0.00 sec)
挺好看的。但是,发送数据
仍然需要 25 秒。
解释上述查询的扩展:
mysql> EXPLAIN EXTENDED SELECT COUNT(*) FROM songs INNER JOIN popular_songs USE INDEX FOR JOIN (songId) ON popular_songs.songId = songs.songId;
+----+-------------+---------------+--------+---------------+---------+---------+-----------------------------+---------+----------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+---------------+--------+---------------+---------+---------+-----------------------------+---------+----------+-------------+
| 1 | SIMPLE | popular_songs | index | songId | songId | 8 | NULL | 2684407 | 100.00 | Using index |
| 1 | SIMPLE | songs | eq_ref | PRIMARY | PRIMARY | 8 | itunes.popular_songs.songId | 1 | 100.00 | Using index |
+----+-------------+---------------+--------+---------------+---------+---------+-----------------------------+---------+----------+-------------+
2 rows in set, 1 warning (0.00 sec)
最佳答案
我的猜测是 songDuration
上的索引让优化器感到困惑。您可以尝试这样表述查询:
SELECT COUNT(*)
FROM songs s
WHERE EXISTS (SELECT 1
FROM popular_songs ps
WHERE ps.songId = s.songId
) AND
s.songDuration > 0;
songDuration
上的索引最好也包含 songId
:songs(songDuration, songId)
。
关于MySQL 在使用 INNER JOIN 时不响应简单查询。特别是 "Sending data"需要太多时间,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/35481265/
我有三张 table 。表 A 有选项名称(即颜色、尺寸)。表 B 有选项值名称(即蓝色、红色、黑色等)。表C通过将选项名称id和选项名称值id放在一起来建立关系。 我的查询需要显示值和选项的名称,而
在mysql中,如何计算一行中的非空单元格?我只想计算某些列之间的单元格,比如第 3-10 列之间的单元格。不是所有的列...同样,仅在该行中。 最佳答案 如果你想这样做,只能在 sql 中使用名称而
关闭。这个问题需要多问focused 。目前不接受答案。 想要改进此问题吗?更新问题,使其仅关注一个问题 editing this post . 已关闭 7 年前。 Improve this ques
我正在为版本7.6进行Elasticsearch查询 我的查询是这样的: { "query": { "bool": { "should": [ {
关闭。这个问题需要多问focused 。目前不接受答案。 想要改进此问题吗?更新问题,使其仅关注一个问题 editing this post . 已关闭 7 年前。 Improve this ques
是否可以编写一个查询来检查任一子查询(而不是一个子查询)是否正确? SELECT * FROM employees e WHERE NOT EXISTS (
我找到了很多关于我的问题的答案,但问题没有解决 我有表格,有数据,例如: Data 1 Data 2 Data 3
以下查询返回错误: 查询: SELECT Id, FirstName, LastName, OwnerId, PersonEmail FROM Account WHERE lower(PersonEm
以下查询返回错误: 查询: SELECT Id, FirstName, LastName, OwnerId, PersonEmail FROM Account WHERE lower(PersonEm
我从 EditText 中获取了 String 值。以及提交查询的按钮。 String sql=editQuery.getText().toString();// SELECT * FROM empl
我有一个或多或少有效的查询(关于结果),但处理大约需要 45 秒。这对于在 GUI 中呈现数据来说肯定太长了。 所以我的需求是找到一个更快/更高效的查询(几毫秒左右会很好)我的数据表大约有 3000
这是我第一次使用 Stack Overflow,所以我希望我以正确的方式提出这个问题。 我有 2 个 SQL 查询,我正在尝试比较和识别缺失值,尽管我无法将 NULL 字段添加到第二个查询中以识别缺失
什么是动态 SQL 查询?何时需要使用动态 SQL 查询?我使用的是 SQL Server 2005。 最佳答案 这里有几篇文章: Introduction to Dynamic SQL Dynami
include "mysql.php"; $query= "SELECT ID,name,displayname,established,summary,searchlink,im
我有一个查询要“转换”为 mysql。这是查询: select top 5 * from (select id, firstName, lastName, sum(fileSize) as To
通过我的研究,我发现至少从 EF 4.1 开始,EF 查询上的 .ToString() 方法将返回要运行的 SQL。事实上,这对我来说非常有用,使用 Entity Framework 5 和 6。 但
我在构造查询来执行以下操作时遇到问题: 按activity_type_id过滤联系人,仅显示最近事件具有所需activity_type_id或为NULL(无事件)的联系人 表格结构如下: 一个联系人可
如何让我输入数据库的信息在输入数据 5 分钟后自行更新? 假设我有一张 table : +--+--+-----+ |id|ip|count| +--+--+-----+ |
我正在尝试搜索正好是 4 位数字的 ID,我知道我需要使用 LENGTH() 字符串函数,但找不到如何使用它的示例。我正在尝试以下(和其他变体)但它们不起作用。 SELECT max(car_id)
我有一个在 mysql 上运行良好的 sql 查询(查询 + 连接): select sum(pa.price) from user u , purchase pu , pack pa where (
我是一名优秀的程序员,十分优秀!