Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-27755

As a heavy WCM user, I'd like to see much shorter response times when I'm using the web content list portlet

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 6.2.0 CE M3
    • Fix Version/s: 6.2.0 CE M3
    • Labels:
      None
    • Environment:
      Tomcat 7 + MySQL 5.5. Portal 6.2.x GIT ID: 06e81d2c98901c0ba546e9eb61b49e379d80b6a4.
      Tomcat 7 + Oracle 11g. Portal 6.2.x GIT ID: 06e81d2c98901c0ba546e9eb61b49e379d80b6a4.
    • Epic/Theme:
    • Business Value:
      5

      Description

      Proposals for optimizing SQL queries in the web content list.

      1) JournalArticleFinder.countByC_G_F_C_A_V_T_D_C_T_S_T_D_R

      There is no need to calculate the lastest version by using the combination of GROUP BY and MAX(version), because it's enough to count each matching articleId with a COUNT(DISTINCT ...)

      2) JournalArticleFinder.findByG_U_C
      3) JournalArticleFinder.findByG_C_S
      4) JournalArticleFinder.findByC_G_F_C_A_V_T_D_C_T_S_T_D_R

      These can be optimized by materializing the latest version in a separate entity and using an inner join instead of the combination of GROUP BY and MAX(version).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              laszlo.csontos Laszlo Csontos (Inactive)
              Reporter:
              zsigmond.rab Zsigmond Rab
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  6.2.0 CE M3