[SERVER-10658] Journal Per Database Created: 31/Aug/13 Updated: 10/Dec/14 Resolved: 02/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | 2.5.2 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Brandon Hedge | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Journal, Performance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
There may be a potential benefit with performance of some workloads on MongoDB if there is a journal per database file. That way physical I/O could be segregated and the server can handle more user workloads. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 02/Sep/13 ] |
|
duplicate of |