[SERVER-659] Locking indexes to RAM - Preallocation of Memory Created: 23/Feb/10 Updated: 17/May/10 Resolved: 17/May/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Performance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Tobias O. | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
an option to mlock indexes or preallocate memory would be nice. in our case we want to have all our data in mem for quicker access, the option to preallocate memory to the mongo daemon or strictly set locking indexes to memory would be very helpful. just some way to ensure that the data and/or indexes are fully copied to mem would make my life much easier... thanks! |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 23/Feb/10 ] |
|
if data > ram blocks get paged in/out based on LRU the os will give mmap data as much ram as possible |
| Comment by Tobias O. [ 23/Feb/10 ] |
|
what would happen if data > ram? well the serverStatus is of course for now good enough... |
| Comment by Eliot Horowitz (Inactive) [ 23/Feb/10 ] |
|
if your data set < ram it should always stay in ram. |
| Comment by Tobias O. [ 23/Feb/10 ] |
|
some way to "know" that its in ram and stays there would be nice. |
| Comment by Eliot Horowitz (Inactive) [ 23/Feb/10 ] |
|
are you concerned with it getting swapped out or knowing when an instance is totally in ram and ready? |