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?
Log in to post a comment.