[SERVER-3752] padding factor overcompaction and related needed improvements Created: 03/Sep/11  Updated: 06/Dec/22  Resolved: 14/Sep/18

Status: Closed
Project: Core Server
Component/s: MMAPv1, Storage
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dwight Merriman Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-9933 add the ability to set a collection's... Closed
Related
related to SERVER-3564 new $archive update operator to reduc... Closed
related to SERVER-1810 ability to set minimum allocation siz... Closed
related to SERVER-4018 Add option to compact command to leav... Closed
is related to SERVER-12225 Allow query filter for compact operation Closed
is related to SERVER-15373 Optimization for insert only work loads Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

The compact command leaves no padding; it should have as an option to keep some, probably the same factor that what was already there.
UPDATE: SERVER-4018 adds an option to preserve padding on compaction (available in 2.6).

Initial sync in replication will result in fully packed documents, which is bad.

Repair will result in fully packed documents, which is bad.

Imports should have some options to be sensitive to having some padding, or some intelligence.

Padding factor should be easily viewable.

update docs when done


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