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="===============3803508621401091545=="
MIME-Version: 1.0
To: allura-dev@incubator.apache.org
From: "Dave Brondsema" <brondsem@users.sf.net>
Reply-To: "[allura:tickets] " <4397@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #4397 Run timeline aggregations in the background
 with taskd
Message-ID: 
 </p/allura/tickets/4397/4bfe6c1f4a4eadf6ed553f778c1fb62bcc24d331.tickets@allura.p.sourceforge.net>
In-Reply-To: <4fdb77fe1be1ce660b000074.tickets@allura.p.sourceforge.net>
References: <4fdb77fe1be1ce660b000074.tickets@allura.p.sourceforge.net>
Date: Tue, 03 Dec 2013 18:30:53 +0000

--===============3803508621401091545==
Content-Type: multipart/alternative;
 boundary="===============1273991441274252776=="
MIME-Version: 1.0

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

- **Size**: 2 --> 4


---

** [tickets:#4397] Run timeline aggregations in the background with taskd**

**Status:** open
**Labels:** v2 activitystreams 
**Created:** Fri Jun 15, 2012 05:59 PM UTC by Tim Van Steenburgh
**Last Updated:** Tue Dec 03, 2013 06:29 PM UTC
**Owner:** nobody

Once the volume ramps up, we probably won't want to be doing timeline aggregations on demand if we can help it. Find good spots to fire off aggregations in the background using taskd, so that when an activitystream page is requested, the cached timeline can just be pulled from mongo w/o doing an aggregation.

For users, a good spot to do this might be on login. For projects, not sure...needs more thought.

Do we need to worry about two aggregations for the same node running at the same time?


---

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.
--===============1273991441274252776==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><ul>
<li><strong>Size</strong>: 2 --&gt; 4</li>
</ul>
<hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/4397/">[tickets:#4397]</a> Run timeline aggregations in the background with taskd</strong></p>
<p><strong>Status:</strong> open<br />
<strong>Labels:</strong> v2 activitystreams <br />
<strong>Created:</strong> Fri Jun 15, 2012 05:59 PM UTC by Tim Van Steenburgh<br />
<strong>Last Updated:</strong> Tue Dec 03, 2013 06:29 PM UTC<br />
<strong>Owner:</strong> nobody</p>
<p>Once the volume ramps up, we probably won't want to be doing timeline aggregations on demand if we can help it. Find good spots to fire off aggregations in the background using taskd, so that when an activitystream page is requested, the cached timeline can just be pulled from mongo w/o doing an aggregation.</p>
<p>For users, a good spot to do this might be on login. For projects, not sure...needs more thought.</p>
<p>Do we need to worry about two aggregations for the same node running at the same time?</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>
--===============1273991441274252776==--

--===============3803508621401091545==--