roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kohei Nozaki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ROL-2092) Optimizing the query that loads the comments in the Admin UI
Date Sat, 09 Jan 2016 02:13:39 GMT

    [ https://issues.apache.org/jira/browse/ROL-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090342#comment-15090342
] 

Kohei Nozaki commented on ROL-2092:
-----------------------------------

BTW, I couldn't duplicate the query on Matt's screenshot which involves many joins (many {{weblogcategory}},
etc) on my environment. Any idea  how can I do it? In my environment, the query is much simpler
as follows:

SELECT t0.id AS a1, t0.content AS a2, t0.contenttype AS a3, t0.email AS a4, t0.name AS a5,
t0.notify AS a6, t0.plugins AS a7, t0.posttime AS a8, t0.referrer AS a9, t0.remotehost AS
a10, t0.status AS a11, t0.url AS a12, t0.useragent AS a13, t0.entryid AS a14 FROM roller_comment
t0, weblogentry t1 WHERE ((t1.websiteid = 'f0588427-f2ca-4843-ac87-bbb31aa6013c') AND (t1.id
= t0.entryid)) ORDER BY t0.posttime DESC LIMIT 31 OFFSET 0;


> Optimizing the query that loads the comments in the Admin UI
> ------------------------------------------------------------
>
>                 Key: ROL-2092
>                 URL: https://issues.apache.org/jira/browse/ROL-2092
>             Project: Apache Roller
>          Issue Type: Improvement
>          Components: Data Model & JPA Backend
>    Affects Versions: 5.1.2
>            Reporter: Kohei Nozaki
>            Assignee: Roller Unassigned
>            Priority: Minor
>         Attachments: roller-slowquery.png
>
>
> Listing comments in the admin UI seems useless due to terribly slow query in a Roller
instance which has over ten thousands comments. Originally reported by Matt:
> http://mail-archives.apache.org/mod_mbox/roller-dev/201503.mbox/%3cCAFhCnT4HTH01ghKnTthiKPf3ALLfYT1UrqvzXeKm8A_y2bdtpg@mail.gmail.com%3e
> I think many unnecessary joins happen in it, So I believe it can be optimized a way without
altering any of existing roller tables (I guess using {{NEW}} clause in the JPQL might help...).
> Anyway I wish I could see the result of {{EXPLAIN}} for the query...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message