Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net
 designates 216.34.181.60 as permitted sender)
Content-Type: multipart/related;
 boundary="===============4459991230413957173=="
MIME-Version: 1.0
To: "[allura:tickets] " <6735@tickets.allura.p.re.sf.net>
From: "Dave Brondsema" <brondsem@users.sf.net>
Reply-To: "[allura:tickets] " <6735@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #6735 Cache markdown rendering results -> posts
 first
Message-ID: 
 </p/allura/tickets/6735/30c23f2e84b873e4ab1e89c94b6bb8238d4129a7.tickets@allura.p.sourceforge.net>
Date: Fri, 04 Oct 2013 19:02:09 +0000

--===============4459991230413957173==
Content-Type: multipart/alternative;
 boundary="===============4218115243845132368=="
MIME-Version: 1.0

--===============4218115243845132368==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

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 sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
--===============4218115243845132368==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><p>Let's store this as a field right on the post artifact, so it's available to check during the render call easily.</p>
<p>Only cache when needed, e.g. render time above a configurable threshold value.</p>
<hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/6735/">[tickets:#6735]</a> Cache markdown rendering results -&gt; posts first</strong></p>
<p><strong>Status:</strong> open<br />
<strong>Labels:</strong> performance <br />
<strong>Created:</strong> Thu Oct 03, 2013 07:00 PM UTC by Dave Brondsema<br />
<strong>Last Updated:</strong> Thu Oct 03, 2013 07:00 PM UTC<br />
<strong>Owner:</strong> nobody</p>
<p>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.</p>
<p>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.</p>
<p>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 &amp; tickets for example)</p>
<hr />
<p>Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to <a href="https://sourceforge.net/p/allura/tickets/">https://sourceforge.net/p/allura/tickets/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/allura/admin/tickets/options.">https://sourceforge.net/p/allura/admin/tickets/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============4218115243845132368==--

--===============4459991230413957173==--