activitystream:tv/4397
allura:tv/4397
Before testing run:
mongo activitystream --eval 'db.nodes.update({}, {"$set":
{"is_aggregating": false}}, false, true);'
You can tell if an on-demand aggregation happened (when viewing a timeline) by
tailing `stats.log` and searching for `create_timeline` calls. If there are
none, the timeline was up-to-date and served directly from mongo.
---
** [tickets:#4397] Run timeline aggregations in the background with taskd**
**Status:** code-review
**Labels:** v2 activitystreams
**Created:** Fri Jun 15, 2012 05:59 PM UTC by Tim Van Steenburgh
**Last Updated:** Fri Dec 13, 2013 05:53 AM 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 [email protected] 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.
