[SERVER-13345] Provide an option to disable journal compression Created: 25/Mar/14  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: Improvement Priority: Minor - P4
Reporter: Mark Callaghan Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 2
Labels: journal
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-9802 Single-threaded journal compression b... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

I get better throughput for some workloads after disabling journal compression. At least one other JIRA was already open for perf problems with this – SERVER-9802.

My request is for a configuration option to disable it. If that is not feasible then the current code should be more clever about hiding latency from compression, like starting to compress earlier rather than in Journal::journal.

From other testing I see that MongoDB writes much more to the journal than InnoDB writes to its redo log so making MongoDB less verbose will also help. See http://smalldatum.blogspot.com/2014/03/redo-logs-in-mongodb-and-innodb.html


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