[SERVER-16625] Improve WiredTiger heap usage Created: 22/Dec/14 Updated: 05/Mar/15 Resolved: 05/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eitan Klein | Assignee: | Eitan Klein |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
I have the following observations from WiredTiger stack that i investigated: 1) WT use calloc for heap operations, malloc should be cheaper to use. 2) I also suggest using Low fragmentation heap (http://msdn.microsoft.com/en-us/library/windows/desktop/aa366750%28v=vs.85%29.aspx), we have something like LFH implemented in MMAP 1) i opened this as FYI, in case we have to improve this now Eitan |
| Comments |
| Comment by Alvin Richards (Inactive) [ 22/Dec/14 ] |
|
thanks for logging. Bear in mind and info you put in here is public by -Alvin On Mon, Dec 22, 2014 at 5:52 AM, Eitan Klein (JIRA) <jira@mongodb.org> |