Uploaded image for project: 'CMS'
  1. CMS
  2. CMS-3311

Performance : think about a partial cache for dynamic pages

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 3.4
    • 3.3
    • None
    • None

      A dynamic page is made of :
      1) aggregation of static and dynamic part from zones (content, cacheable services, non-cacheable services)
      2) dynamic inputdata
      3) presentation (skining through xsl)

      Currently serving a page with a complex content aggregation and a search service, make this page very long to load because it is non cacheable...

      A way to accelerate this could be to

      • activate cocoon page on static rendering pipelines. But how to clean this correctly ?
      • make a manuel cache in the PageGenerator (that would be clean, when the site caches are cleaned). This cache would be for 'live' workspace only.

      My preference is for the second solution that can be implemented independantly of every service and content impl

          [CMS-3311] Performance : think about a partial cache for dynamic pages

          Two caches will be added : one for InputData and one for ZoneItem

          Cédric Damioli added a comment - Two caches will be added : one for InputData and one for ZoneItem

            ngavalda Nicolas Gavalda (Inactive)
            raphael Raphaël Franchet
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: