#6735 Cache markdown rendering results -> posts first

asf_release_1.1.0
closed
General
Cory Johns
2014-10-30
2013-10-03
Dave Brondsema
No

Some markdown content (e.g. lots of HTML) can take a while to render. Let's cache the results, and serve the HTML result directly for future requests.

Scope: let's limit to just Post comments first, since those can have many show up on one page. Plan for the future where any artifact might have a cached result that can be served up.

Cache invalidation: need to invalidate when the content changes, of course. Also macros and artifact-references can be incorrect when those remote content changes. I don't think we have a way to invalidate based on those easily. Keeping scope to comment posts will help, since those don't have many macros (e.g. compared to wiki & tickets for example)

Related

Tickets: #6207

Discussion

  • Dave Brondsema
    Dave Brondsema
    2013-10-04

    • Size: --> 2
     
  • Dave Brondsema
    Dave Brondsema
    2013-10-04

    Let's store this as a field right on the post artifact, so it's available to check during the render call easily.

    Only cache when needed, e.g. render time above a configurable threshold value.

     
    • status: open --> in-progress
    • assigned_to: Tim Van Steenburgh
     
  • allura:tv/6735
    configtree:tv/6735

     
    • status: in-progress --> code-review
     

  • Anonymous
    2013-10-13

    Originally by: *anonymous

    In-progress code review

     
  • Cory Johns
    Cory Johns
    2013-10-15

    • QA: Cory Johns
     
  • Cory Johns
    Cory Johns
    2013-10-15

    • status: code-review --> closed