以下查询需要大约14秒才能完成。我有一个包含1M条目的人员表。任何人都可以建议我如何使查询更快,并减少执行时间,如1,2或3秒?我附上下面的解释详情。
SELECT p.id,
COUNT(CASE WHEN p.active=1 THEN 1 END) AS active_users_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') = DATE_FORMAT(NOW(),'%Y-%m-%d') THEN 1 END) AS today_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') = DATE_FORMAT(DATE_SUB(NOW(),INTERVAL 1 DAY), '%Y-%m-%d') THEN 1 END) AS yesterday_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL DAY(LAST_DAY(NOW())) DAY) AND CURDATE() THEN 1 END) AS month_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL 1 YEAR) AND CURDATE() THEN 1 END) AS year_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL 7 DAY) AND CURDATE() THEN 1 END) AS week_install_count,
COUNT('x') AS total_users_count
FROM person p
WHERE p.app_id IN (SELECT p2.id FROM project p2 ) GROUP BY p.app_id
返回239行
执行时间:13.504秒 转移时间:0.001秒 总时间:13.505秒
为人和项目创建表
person CREATE TABLE `person` (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`device_push_token` longtext NOT NULL,
`created_date` datetime NOT NULL,
`since_last_login` datetime NOT NULL,
`platform` smallint(6) NOT NULL,
`hwid` varchar(255) NOT NULL,
`app_id` bigint(20) NOT NULL,
`since_last_push` datetime NOT NULL,
`no_of_pushes` smallint(6) NOT NULL DEFAULT '0',
`language` varchar(50) DEFAULT NULL,
`timezone` bigint(20) DEFAULT '0',
`since_last_hour_push` datetime DEFAULT NULL,
`version` bigint(20) NOT NULL DEFAULT '1',
`active` tinyint(1) NOT NULL DEFAULT '1',
PRIMARY KEY (`id`),
UNIQUE KEY `hwid` (`hwid`,`app_id`),
KEY `fk_person_platform` (`platform`),
KEY `fk_person_project` (`app_id`),
CONSTRAINT `fk_person_platform` FOREIGN KEY (`platform`) REFERENCES `platform` (`id`),
CONSTRAINT `fk_person_project` FOREIGN KEY (`app_id`) REFERENCES `project` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=1310384 DEFAULT CHARSET=latin1
project CREATE TABLE `project` (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`unique_id` varchar(300) NOT NULL,
`name` longtext NOT NULL,
`description` longtext,
`ios_configure` bigint(20) DEFAULT NULL,
`android_configure` bigint(20) DEFAULT NULL,
`freq_push` bigint(20) DEFAULT NULL,
`hour_push` bigint(20) DEFAULT NULL,
`push_sent` bigint(20) DEFAULT '0',
`push_opened` bigint(20) DEFAULT '0',
`version` bigint(20) NOT NULL DEFAULT '1',
`created_date` datetime NOT NULL,
`updated_date` datetime NOT NULL,
`active` tinyint(1) NOT NULL DEFAULT '1',
`project_apprater` bigint(20) DEFAULT NULL,
`type` smallint(6) NOT NULL DEFAULT '1',
`status` bigint(20) DEFAULT '1',
PRIMARY KEY (`id`),
UNIQUE KEY `unique_id` (`unique_id`),
KEY `fk_project_ios_config` (`ios_configure`),
KEY `fk_project_android_config` (`android_configure`),
KEY `fk_project_freq_push` (`freq_push`),
KEY `fk_project_hour_push` (`hour_push`),
KEY `fk_project_apprater` (`project_apprater`),
KEY `fk_project_platform` (`type`),
KEY `name` (`status`),
CONSTRAINT `fk_project_android_config` FOREIGN KEY (`android_configure`) REFERENCES `project_configure_android` (`id`),
CONSTRAINT `fk_project_apprater` FOREIGN KEY (`project_apprater`) REFERENCES `project_apprater` (`id`),
CONSTRAINT `fk_project_freq_push` FOREIGN KEY (`freq_push`) REFERENCES `freq_push` (`id`),
CONSTRAINT `fk_project_hour_push` FOREIGN KEY (`hour_push`) REFERENCES `hour_push` (`id`),
CONSTRAINT `fk_project_ios_config` FOREIGN KEY (`ios_configure`) REFERENCES `project_configure_ios` (`id`),
CONSTRAINT `fk_project_platform` FOREIGN KEY (`type`) REFERENCES `platform` (`id`),
CONSTRAINT `name` FOREIGN KEY (`status`) REFERENCES `project_status` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=313 DEFAULT CHARSET=latin1
id select_type table type possible_keys key key_len ref rows Extra
1 PRIMARY p index \N fk_person_project 8 \N 1158770 Using where
2 DEPENDENT SUBQUERY p2 unique_subquery PRIMARY PRIMARY 8 func 1 Using index
更新了完整查询
SELECT
p3.id AS id,
COALESCE(pug.active_users_count, 0) AS userCount,
p3.unique_id AS uniqueId,
p3.name,
p3.description,
DATE_FORMAT(p3.created_date, '%m-%d-%Y %T') AS createdDate,
p3.android_configure AS androidConfigure,
p3.ios_configure AS iosConfigure,
(SELECT
fp.active
FROM
freq_push fp
WHERE fp.id = p3.freq_push) AS freqActive,
(SELECT
hp.active
FROM
hour_push hp
WHERE hp.id = p3.hour_push) AS hourActive,
COALESCE(pug.total_users_count, 0) AS totalUserCount,
COALESCE(pug.today_install_count, 0) AS todayInstallCount,
COALESCE(pug.yesterday_install_count, 0) AS yesterdayInstallCount,
COALESCE(pug.month_install_count, 0) AS monthInstallCount,
COALESCE(pug.year_install_count, 0) AS yearInstallCount,
COALESCE(pug.week_install_count, 0) AS weekInstallCount,
(SELECT
plat.name
FROM
platform plat
WHERE plat.id = p3.type) AS project_type ,
ps.name
FROM
(SELECT
p.app_id,
COUNT(
CASE
WHEN p.active = 1
THEN 1
END) AS active_users_count,
COUNT(
CASE
WHEN DATE(p.created_date) = CURDATE()
THEN 1
END
) AS today_install_count,
COUNT(
CASE
WHEN DATE(p.created_date) = DATE(DATE_SUB(NOW(), INTERVAL 1 DAY))
THEN 1
END
) AS yesterday_install_count,
COUNT(
CASE
WHEN DATE(p.created_date) BETWEEN DATE_SUB(
CURDATE(),
INTERVAL DAY(LAST_DAY(NOW())) DAY
)
AND CURDATE()
THEN 1
END
) AS month_install_count,
COUNT(
CASE
WHEN DATE(p.created_date) BETWEEN DATE_SUB(CURDATE(), INTERVAL 1 YEAR)
AND CURDATE()
THEN 1
END
) AS year_install_count,
COUNT(
CASE
WHEN DATE(p.created_date) BETWEEN DATE_SUB(CURDATE(), INTERVAL 7 DAY)
AND CURDATE()
THEN 1
END
) AS week_install_count,
COUNT('x') AS total_users_count
FROM
person p
INNER JOIN project p2
ON p.app_id = p2.id
GROUP BY p.app_id) AS pug
RIGHT JOIN project p3
ON p3.id = pug.app_id
INNER JOIN project_status ps
ON p3.status = ps.id
ORDER BY userCount DESC,
createdDate DESC
答案 0 :(得分:1)
从以前的版本修改此答案。基本上 Mark B 正好在comments中。幸运的是OP已经取得了进展,时间已经从13秒减少到6点以下.OP表示(根据他自己的答案和聊天中的评论)如果时间可以缩短到1秒以下,他会考虑其他方法。就像我和他谈论的一样,关于接受一些陈旧的指标,他可以选择陈旧的持续时间持续多长时间。在用户的陈旧和速度之间进行权衡。
所以这是一种方法。
使用Create Event创建一个事件,该事件会在他选择的每个nnn(时间段)Interval
内自动触发。该事件更新了他的最终用户访问的表。事件本身从他的答案中运行他的查询,您将看到嵌入在下面的事件中。
create table appIdMetrics
( -- this is the table Users hit against
appId int not null primary key,
active_users_count int not null,
today_install_count int not null,
yesterday_install_count int not null,
month_install_count int not null,
year_install_count int not null,
week_install_count int not null,
total_users_count int not null
);
create table evt_appIdMetrics
( -- this is the worktable that only the Event uses
-- while it puts together the refreshed data
-- perhaps once every 5 minutes
appId int not null primary key,
active_users_count int not null,
today_install_count int not null,
yesterday_install_count int not null,
month_install_count int not null,
year_install_count int not null,
week_install_count int not null,
total_users_count int not null
);
drop event updateAppIdMetrics;
DELIMITER $$
CREATE EVENT updateAppIdMetrics
ON SCHEDULE
EVERY 5 MINUTE
DO BEGIN
truncate table evt_appIdMetrics; -- this is the table that only the evt has access to
-- time to refresh this table (approx 6 seconds)
-- 280 rows (count as per OP comments)
insert into evt_appIdMetrics
(appId,active_users_count,today_install_count,yesterday_install_count,
month_install_count,year_install_count,week_install_count,total_users_count)
select p.app_id,
COUNT(CASE WHEN p.active=1 THEN 1 END) AS active_users_count,
COUNT(CASE WHEN DATE(p.created_date)= CURDATE() THEN 1 END) AS today_install_count,
COUNT(CASE WHEN DATE(p.created_date) = DATE(DATE_SUB(NOW(),INTERVAL 1 DAY)) THEN 1 END) AS yesterday_install_count,
COUNT(CASE WHEN DATE(p.created_date) BETWEEN DATE_SUB(CURDATE(),INTERVAL DAY(LAST_DAY(NOW())) DAY) AND CURDATE() THEN 1 END) AS month_install_count,
COUNT(CASE WHEN DATE(p.created_date) BETWEEN DATE_SUB(CURDATE(),INTERVAL 1 YEAR) AND CURDATE() THEN 1 END) AS year_install_count,
COUNT(CASE WHEN DATE(p.created_date) BETWEEN DATE_SUB(CURDATE(),INTERVAL 7 DAY) AND CURDATE() THEN 1 END) AS week_install_count,
COUNT('x') AS total_users_count
FROM person p
INNER JOIN project p2 ON p.app_id = p2.id
GROUP BY p.app_id;
-- BEGIN LOCK (important)
-- figure out a locking scheme (work-in-progress, not completed yet)
truncate table appIdMetrics; -- this is the table users access
-- the following should take a split second on the approximately 280 rows (count as per OP comments)
insert into appIdMetrics
(appId,active_users_count,today_install_count,yesterday_install_count,
month_install_count,year_install_count,week_install_count,total_users_count)
select appId,active_users_count,today_install_count,yesterday_install_count,
month_install_count,year_install_count,week_install_count,total_users_count
from evt_appIdMetrics;
-- complete locking schema (work-in-progress, not completed yet)
-- END LOCK (important)
END;$$
DELIMITER ;
-- evt creation succeeded by passing Syntax Error check
用户与表appIdMetrics
进行互动。当我有机会时,我会调整所提到的锁定方案。用户的用户体验应该是瞬间的。数据刷新间隔可通过OP调整为陈旧因子。根据我的经验,该事件将在第一次第一时间段之后第一次开启。这意味着5分钟。
我将稍微提供一个事件管理链接。 修改:here确实如此。必须启用事件。
答案 1 :(得分:0)
也许你可以尝试加入这个表。但我不确定这可以将执行时间缩短到3秒。
SELECT p.id,
COUNT(CASE WHEN p.active=1 THEN 1 END) AS active_users_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') = DATE_FORMAT(NOW(),'%Y-%m-%d') THEN 1 END) AS today_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') = DATE_FORMAT(DATE_SUB(NOW(),INTERVAL 1 DAY), '%Y-%m-%d') THEN 1 END) AS yesterday_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL DAY(LAST_DAY(NOW())) DAY) AND CURDATE() THEN 1 END) AS month_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL 1 YEAR) AND CURDATE() THEN 1 END) AS year_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL 7 DAY) AND CURDATE() THEN 1 END) AS week_install_count,
COUNT('x') AS total_users_count
FROM person p
INNER JOIN project p2 ON p.app_id = p2.id
GROUP BY p.app_id
答案 2 :(得分:0)
在这个查询中我理解的是,你需要过去一年的所有计数而不是非常旧的数据。在这种情况下,如果项目表中有project_date,那么您可以限制子查询中的ID,这可能有助于比旧查询更好。
SELECT p.id,
COUNT(CASE WHEN p.active=1 THEN 1 END) AS active_users_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') =DATE_FORMAT(NOW(),'%Y-%m-%d') THEN 1 END) AS today_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') =DATE_FORMAT(DATE_SUB(NOW(),INTERVAL 1 DAY), '%Y-%m-%d') THEN 1 END) AS yesterday_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL DAY(LAST_DAY(NOW())) DAY) AND CURDATE() THEN 1 END) AS month_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL 1 YEAR) AND CURDATE() THEN 1 END) AS year_install_count,
COUNT(CASE WHEN DATE_FORMAT(p.created_date,'%Y-%m-%d') BETWEEN DATE_SUB(CURDATE(),INTERVAL 7 DAY) AND CURDATE() THEN 1 END) AS week_install_count
FROM person p
WHERE p.app_id IN (SELECT p2.id FROM project p2 AND p2.project_date > DATE_SUB(CURDATE(),INTERVAL 1 YEAR))
GROUP BY p.app_id;
现在,您可以单独获取每个项目ID的总数,并与上述计数合并。
SELECT p.id, COUNT('x') AS total_users_count
FROM person p
WHERE p.app_id IN (SELECT p2.id FROM project p2)
GROUP BY p.app_id;
希望这会有所帮助。
答案 3 :(得分:0)
以下查询执行时间减少到5秒。你们能解释一下为什么从DATE_FORMAT()到DATE()的改变会带来这种显着的改善吗?
brew reinstall postgis
答案 4 :(得分:0)
另一个优化思路......在子查询中,计算一次多少天String output = input.replaceAll("(^|\\W)\\w{1,3}($|\\W)", " ");
,作为整数。然后在外部查询中做更有效的
created_date
请注意age <= 365 AS year_install_count,
age <= 7 AS weel_install_count,
...
是一个“布尔”,对于true显示为“1”,对于false显示为“0”。因此,无需重复x <= y
,DATE_SUB
或更晚DATE_FORMAT
等。
要获取COALESCE
,请尝试age
或使用DATEDIFF(created_date, CURRDATE)
。警告:它可能会被1点关闭。