[DOCS-4894] Pre-Aggregated Reports use case doc needs changing to reflect WiredTiger use Created: 03/Mar/15  Updated: 29/Oct/17  Resolved: 04/Oct/16

Status: Closed
Project: Documentation
Component/s: ecosystem
Affects Version/s: None
Fix Version/s: mongodb-3.0

Type: Improvement Priority: Major - P3
Reporter: Paul Done Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: aggregation, storage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-7310 Pre-Aggregated Reports use case is MM... Closed
Related
is related to DOCS-1582 Update Use Cases To use Aggregation F... Closed
is related to DOCS-3983 Comment on: "mongodb-ecosystem/use-ca... Closed
Participants:
Days since reply: 7 years, 19 weeks, 1 day ago
Epic Link: docs-cleanup-ecosystem
Story Points: 0.25

 Description   

The "Pre-Aggregated Reports" use case doc page http://docs.mongodb.org/ecosystem/use-cases/pre-aggregated-reports/ is one of the most important use case pages for MongoDB, and is used and reference by many customers/users, especially w.r.t. to time-series type usage patterns, often found in Financial Services and IoT.

With the introduction of WiredTiger in MongoDB version 3.0, some of the advice in this page may no longer be applicable and may need to be marked as applying to MMAPv1 use only.

The page defines 4 key patterns:
1. Pre-aggregation (update averages/mins/maxs for each consumed event rather than recording raw event).
2. Bucketing (grouping sets of records together, eg. by day, for fast subsequent access - the pattern to deal with consuming lots of fine grained events and then servicing analytics/reports that want to retrieve coarse grained data).
3. Pre-allocation (aka. pre-padding, to avoid excessive document growth and re-allocation)
4. Intra-document-hierarchy (to prevent event ingestion latencies from increasing as the time of each day increases)

Note: These patterns are also documented in chapter 4 of the book "MongoDB Applied Design Patterns" by Rick Copeland (O'Reilly)

With the introduction of WiredTiger, it is likely that pattern 3 (Pre-allocation) is no longer required and perhaps would even be detrimental, due to the way WiredTiger deals with "in-place updates" internally. Also it could be that pattern 4 (intra-document hierarchy) also adds no value when using WiredTiger (this needs to be validated by someone).

Please update the doc page to indicate which of the 4 patterns should not be applied, when running WiredTiger rather than MMAPv1.



 Comments   
Comment by Githook User [ 04/Oct/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-4894 rename filename so url reflects mmapv1 as well
Branch: master
https://github.com/mongodb/docs-ecosystem/commit/76d260cc53182ac7ac46228d78c8e3a993b2b3bc

Comment by Githook User [ 04/Oct/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-4894 updat title and add admonition for MMAPv1 only
Branch: master
https://github.com/mongodb/docs-ecosystem/commit/d27236463908e23281f6ac6f5a0258353c1a42db

Comment by Kay Kim (Inactive) [ 04/Oct/16 ]

Will annotate as MMAPv1 only and update title to reflect MMAPv1 as well.

Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Generated at Thu Feb 08 07:49:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.