如何解决复杂的SQL查询优化
| 我正在尝试优化SQL查询。你能帮助我吗? 基本上,每个用户都通过一个友谊表拥有朋友,并且每个用户都通过一个user_feed_events表拥有许多feed_events。 我正在尝试列出给定用户的朋友的feed_events。应该不是不可能,对吧? :) 如您所见,查询的性能取决于用户有多少个朋友。现在,有150个朋友的用户将花费近7秒钟来执行。 更新:这是我的友谊表的构建方式:create_table \"friendships\",:force => true do |t|
t.integer \"user_id\",:null => false
t.integer \"friend_id\",:null => false
t.datetime \"created_at\"
t.datetime \"accepted_at\"
end
add_index \"friendships\",[\"friend_id\"],:name => \"index_friendships_on_friend_id\"
add_index \"friendships\",[\"user_id\"],:name => \"index_friendships_on_user_id\"
首先,我要求Rails给我用户的朋友的用户ID的列表,然后在实际查询中使用此字符串。
friends_id = current_user.friends.collect {|f| f.id}.join(\",\")
sql = \"
SELECT
DISTINCT feed_events.id,feed_events.event_type,feed_events.type_id,feed_events.data,feed_events.created_at,feed_events.updated_at,user_feed_events.user_id
FROM feed_events
LEFT JOIN user_feed_events
ON feed_events.id = user_feed_events.feed_event_id
WHERE user_feed_events.user_id IN (#{friends_id})
ORDER BY feed_events.created_at DESC\"
然后,我严格执行查询(将其分页并限制为30个结果):
@events = FeedEvent.paginate_by_sql(sql,:page => params[:page],:per_page => 30)
更新2:这里是解释分析输出:
SQL> EXPLAIN ANALYZE (SELECT DISTINCT feed_events.id,user_feed_events.user_id FROM user_feed_events INNER JOIN feed_events ON feed_events.id = user_feed_events.feed_event_id WHERE user_feed_events.user_id IN (1,7,9,8,14,15,20,35,40,39,41,42,57,84,98,109,121,74,129,64,137,77,172,182,206,201,284,31,94,232,311,168,30,114,50,174,419,403,438,464,423,513,351,349,385,622,751,359,809,838,844,962,831,786,896,1001,992,998,990,256,67,623,957,1226,1060,1009,1490,132,1467,1672,619,1459,1466,993,1599,1365,607,1381,1714,1154,2032,2230,2240,2354,598,2345,1804,634,1900,2652,1975,2164,1759,3288,1004,3487,3507,3542,3566,514,3787,3137,3803,3090,4012,855,17,2026,1463,335,1000,935,5,12,10,13,19,18,16,22,34,27,29,59,126,90,46,23,63,291,134,229,107,439,521) ORDER BY feed_events.created_at DESC)
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| QUERY PLAN |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Unique (cost=6090.87..6162.93 rows=18014 width=389) (actual time=1641.210..1733.010 rows=29691 loops=1) |
| -> Sort (cost=6090.87..6099.88 rows=18014 width=389) (actual time=1641.206..1670.882 rows=29694 loops=1) |
| Sort Key: feed_events.created_at,feed_events.id,user_feed_events.user_id |
| Sort Method: quicksort Memory: 17755kB |
| -> Hash Join (cost=3931.63..5836.21 rows=18014 width=389) (actual time=258.541..361.345 rows=29694 loops=1) |
| Hash Cond: (user_feed_events.feed_event_id = feed_events.id) |
| -> Bitmap Heap Scan on user_feed_events (cost=926.64..2745.66 rows=18014 width=8) (actual time=6.930..42.367 rows=29694 loops=1) |
| Recheck Cond: (user_id = ANY (\'{1,521}\'::integer[])) |
| -> Bitmap Index Scan on index_user_feed_events_on_user_id (cost=0.00..925.74 rows=18014 width=0) (actual time=6.836..6.836 rows=29694 loops=1) |
| Index Cond: (user_id = ANY (\'{1,521}\'::integer[])) |
| -> Hash (cost=2848.84..2848.84 rows=44614 width=385) (actual time=251.490..251.490 rows=44663 loops=1) |
| -> Seq Scan on feed_events (cost=0.00..2848.84 rows=44614 width=385) (actual time=0.035..77.044 rows=44663 loops=1) |
| Total runtime: 1780.200 ms |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
SQL>
更新#3:问题是,对于我的Rails应用程序,我正在使用has_many_friends插件(https://github.com/swemoney/has_many_friends),它可以照顾我的友谊。它是这样的。我是user_id#6,我正在向user_id#10询问友谊。当用户#10接受我的友谊时,会将新行添加到表中,其中user_id = 6,friend_id =10。如果用户#10询问我友谊的行是:user_id = 10和friend_id = 6。
这意味着,为了找到friends_by_me,我需要在\“ user_id = 6 \”上进行搜索,为了找到friends_for_me,我需要\“ friend_id = 6 \”。为了找到我所有的朋友,我需要搜索两列。这使得创建连接非常复杂!
您将如何处理?
我能想到的唯一选择是:
\"(SELECT
DISTINCT feed_events.id,user_feed_events.user_id
FROM feed_events
INNER JOIN user_feed_events
ON feed_events.id = user_feed_events.feed_event_id
INNER JOIN friendships
ON user_feed_events.user_id = friendships.user_id
WHERE friendships.user_id = 6
AND friendships.accepted_at IS NOT NULL)
UNION DISTINCT
(SELECT
DISTINCT additional_feed_events.id,additional_feed_events.event_type,additional_feed_events.type_id,additional_feed_events.data,additional_feed_events.created_at,additional_feed_events.updated_at,user_feed_events.user_id
FROM feed_events AS additional_feed_events
INNER JOIN user_feed_events
ON additional_feed_events.id = user_feed_events.feed_event_id
INNER JOIN friendships
ON user_feed_events.user_id = friendships.friend_id
WHERE friendships.friend_id = 6
AND friendships.accepted_at IS NOT NULL)
ORDER BY feed_events.created_at DESC\"
但是目前无法正常工作,我也不确定这样做的正确方法!
谢谢,
奥古斯托
解决方法
为什么使用IN列表?为什么不从所选用户开始?另外,我认为您不需要左外部联接:
SELECT
DISTINCT feed_events.id,feed_events.event_type,feed_events.type_id,feed_events.data,feed_events.created_at,feed_events.updated_at,user_feed_events.user_id
FROM
(
select friend_id from friendship where user_id = YOURUSER
UNION
select user_id as friend_id from friendship where friend_id = YOURUSER
) friendship
inner join user_feed_events
on friendship.friend_id = user_feed_events.user_id
inner join feed_events
on user_feed_events.feed_event_id = feed_events.id
ORDER BY feed_events.created_at DESC
如果要保留原始语句并对其进行优化,请使用以下命令:
SELECT
DISTINCT feed_events.id,user_feed_events.user_id
FROM user_feed_events
INNER JOIN feed_events
ON feed_events.id = user_feed_events.feed_event_id
WHERE user_feed_events.user_id IN (#{friends_id})
ORDER BY feed_events.created_at DESC
这将删除不必要的LEFT JOIN。
此外,请确保在用于外键的列上创建了索引。
,好的,因此查询不是您的问题,必须设置数据库,以免花费不超过几微秒的时间。首先,查询。它看起来应该像这样:
SELECT feed_events.id,user_feed_events.user_id
FROM feed_events
INNER JOIN
user_feed_events ON feed_events.id = user_feed_events.feed_event_id
INNER JOIN
user_friends ON user_friends.friend_id = user_feed_events.user_id
WHERE user_friends.user_id = ** The Id of the User in Question **
ORDER BY feed_events.created_at DESC
接下来,您需要确保Id列是主键,并且在user_friends表中对诸如(friend_id,user_id)之类的东西具有唯一索引。顺便说一句,我只是编造了这些名字,我试图猜测一下您所说的存储友谊的表。
,select distinct fe.id,fe.event_type,fe.type_id,fe.data,fe.created_at,fe.updated_at,ufe.user_id
from friendships as f
inner join user_feed_events as ufe on f.friend_id = ufe.user_id
inner join feed_events as fe on ufe.user_id = fe.id
where f.user_id = 6 and f.accepted_at is not null
order by fe.created_at desc
不知道这里是否真的需要区分。查询返回指定用户的朋友的供稿事件。我希望;)
编辑。
出现的解决方案与Daniel Hilgarth提出的解决方案几乎相同。
,在WHERE
子句中使用子SELECT
来构建IN()
调用的提要事件列表。像这样(未经测试):
SELECT fe.id,ufe.user_id
FROM feed_events AS fe,user_feed_events AS ufe
WHERE TRUE = TRUE
AND fe.id = ufe.feed_event_id
AND ufe.user_id = :user_id
AND fe.id IN((
SELECT ufe.feed_event_id
FROM user_feed_events AS ufe,user_friends AS uf
WHERE uf.friend_id = :user_id
))
ORDER BY feed_events.created_at DESC;
我很想知道ѭ13的样子。
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。