Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E108F1077F for ; Fri, 13 Dec 2013 05:54:25 +0000 (UTC) Received: (qmail 68445 invoked by uid 500); 13 Dec 2013 05:54:25 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 68390 invoked by uid 500); 13 Dec 2013 05:54:24 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 68374 invoked by uid 99); 13 Dec 2013 05:54:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Dec 2013 05:54:23 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Dec 2013 05:54:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:References:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=5d1luvG3OmpN+hj8s80RZ2sLFb8PpdJCDUCebyAd3OA=; b=UiU68o5zFpQ56Jh6gWDJueoR+ZMpeK2hX3/etinTPdYXq0f54B9GOWGmKilEXkdetZWUUgRHF+Pmuc1f0v445UX1W0KHcVCKVNPp2vUmlrXkLIFb65KP9teA/sKvPHC6oEwjMJwm4/suh+aMsSl6PEaZvGhbs9PJVGXYs81pXu8=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VrLhE-0007fv-Tb for allura-dev@incubator.apache.org; Fri, 13 Dec 2013 05:53:56 +0000 Content-Type: multipart/related; boundary="===============2801702414880568611==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Tim Van Steenburgh" 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:

In-Reply-To: <4fdb77fe1be1ce660b000074.tickets@allura.p.sourceforge.net> References: <4fdb77fe1be1ce660b000074.tickets@allura.p.sourceforge.net> Date: Fri, 13 Dec 2013 05:53:56 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============2801702414880568611== Content-Type: multipart/alternative; boundary="===============5006513499550203840==" MIME-Version: 1.0 --===============5006513499550203840== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **status**: open --> in-progress - **assigned_to**: Tim Van Steenburgh --- ** [tickets:#4397] Run timeline aggregations in the background with taskd** **Status:** in-progress **Labels:** v2 activitystreams **Created:** Fri Jun 15, 2012 05:59 PM UTC by Tim Van Steenburgh **Last Updated:** Wed Dec 04, 2013 07:00 PM UTC **Owner:** Tim Van Steenburgh 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. --===============5006513499550203840== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • status: open --> in-progress
  • assigned_to: Tim Van Steenburgh

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

Status: in-progress
Labels: v2 activitystreams
Created: Fri Jun 15, 2012 05:59 PM UTC by Tim Van Steenburgh
Last Updated: Wed Dec 04, 2013 07:00 PM UTC
Owner: Tim Van Steenburgh

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.

--===============5006513499550203840==-- --===============2801702414880568611==--