[SERVER-4358] Preallocating should be configurable Created: 23/Nov/11  Updated: 06/Dec/22  Resolved: 14/Sep/18

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

Type: Improvement Priority: Major - P3
Reporter: Ross Dickey Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

It would be nice to have preallocated database files be more configurable than "on" and "off". In our environment, we create a database per customer. For each customer that does nothing, we still write a little bit of data to the database, therefore triggering preallocation. So, each idle customer's preallocated file size on disk is 3x what it needs to be.

I know of the noprealloc flag. I would prefer something like preallocat=80%, or 50%, or whatever. That is, a way to tell mongo "don't preallocate a new file until you're actually close to needing it, and here's how close you should be". I recognize the benefit of preallocation, and would like to keep the advantages, without the disadvantage of preallocating files that will never be used.


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