[DOCS-7310] Pre-Aggregated Reports use case is MMAPv1 specific Created: 01/Mar/16  Updated: 17/Nov/17  Resolved: 29/Oct/17

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

Type: Task Priority: Major - P3
Reporter: Kevin Adistambha Assignee: Kay Kim (Inactive)
Resolution: Duplicate Votes: 0
Labels: groom
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-4894 Pre-Aggregated Reports use case doc n... Closed
Participants:
Days since reply: 7 years, 50 weeks, 2 days ago

 Description   

The Pre-Aggregated Reports use case:
https://docs.mongodb.org/ecosystem/use-cases/pre-aggregated-reports/
contains warnings and issues that are MMAPv1-specific without any indication that the issue does not affect WiredTiger.

For example:

There are, however, significant issues with this approach. The most significant issue is that, as you upsert data into the hourly and minute fields, the document grows. Although MongoDB will pad the space allocated to documents, it will need to reallocate these documents multiple times throughout the day, which impacts performance.

This will create confusion on whether padding issues are still relevant on WiredTiger.

Also, pointing people to this documentation could give the impression that the docs are not maintained since WiredTiger is available for a while already.


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