[DOCS-14384] Increase visibility for ephemeralForTest engine Created: 27/Apr/21 Updated: 30/Apr/21 Resolved: 30/Apr/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Feedback | Priority: | Major - P3 |
| Reporter: | Mattia Giuffrida | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 2 years, 40 weeks, 5 days ago | ||||||||
| Description |
DescriptionI recently discovered that MongoDB offers a `ephemeralForTest` engine. This discovery followed issues my team experienced when upgrading the MongoDB instance used by our tests suite to v4.4, since we had to switch to `wiredTiger` as the engine. Suddenly, our test suite was running considerably slower, causing delays in our development. After days of tries to get this solved, from using `tmpfs` to disabling indexes and more, a member of our team finally found a reference to the `ephemeralForTest` engine. I would have expected this engine to be mentioned in the Storage Engines page, but instead it is only mentioned in the v3.2 release notes. Since this engine definitely solved our issue, I'd suggest it should be listed, or at least mentioned, in the Storage Engines page, to save other teams some precious time when they face this issue Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Jeffrey Allen [ 30/Apr/21 ] |
|
Thanks mattia.giuffrida@sensortower.com, closing this one. |
| Comment by Mattia Giuffrida [ 27/Apr/21 ] |
|
Sorry about this duplicate, JIRA's UI was hanging with the "Create Ticket" popup opened and I wasn't sure if this had been saved correctly. This ticket can be safely deleted in favour of |