incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #6735 Cache markdown rendering results -> posts first
Date Fri, 04 Oct 2013 19:02:09 GMT
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.


** [tickets:#6735] Cache markdown rendering results -> posts first**

**Status:** open
**Labels:** performance 
**Created:** Thu Oct 03, 2013 07:00 PM UTC by Dave Brondsema
**Last Updated:** Thu Oct 03, 2013 07:00 PM UTC
**Owner:** nobody

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)


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message