Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-9051

Improve cache performance on public instances

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None
    • cache performance

    Description

      Context

      See the notes from UHZ for pain points and initial findings

      Questions for discovery

      • (How) can we implement a cash flush policy that does not rely on observation?
      • Can we rely on publication instead?
      • UZH does this via the NavigationAwareCacheCleaner.java, which uses a filter for intercepting publish requests instead of relying on observation like we do. Can we leverage this solution?
      • How does that affect eager re-caching?
      • Can we do it in the background? Consistency guarantees?

      Discover notes

       

      Checklists

        Acceptance criteria

        Attachments

          1. exclude-workspace.png
            exclude-workspace.png
            386 kB
          2. NavigationAwareCacheCleaner.java
            4 kB
          3. PublicationFilter.java
            3 kB
          4. PublishFilterEvent.java
            1 kB
          5. threads_report.txt
            310 kB
          6. threads_report-3.txt
            443 kB

          Issue Links

            Activity

              People

                Unassigned Unassigned
                mduerig Michael Duerig
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated: