[SERVER-7570] Add a function to ProcessInfo that checks whether a range of contiguous memory pages are in RAM Created: 06/Nov/12 Updated: 11/Jul/16 Resolved: 14/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.1 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andrea Lattuada (Inactive) | Assignee: | Andrea Lattuada (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
The currently available ProcessInfo::blockInMemory(...) only accepts one page at a time. The mincore function on UNIX and QueryWSEx on Windows accept a range of pages: exposing this functionality makes it possible to know which pages of an entire extent or database file are likely in memory with a single call. |
| Comments |
| Comment by auto [ 14/Nov/12 ] |
|
Author: {u'date': u'2012-11-14T00:40:27Z', u'email': u'redbeard0531@gmail.com', u'name': u'Mathias Stearn'}Message: Merge pull request #324 from utaal/blockInMemory-pagesInMemory
|
| Comment by auto [ 14/Nov/12 ] |
|
Author: {u'date': u'2012-11-13T21:34:57Z', u'email': u'andrea.lattuada@10gen.com', u'name': u'Andrea Lattuada'}Message: |
| Comment by auto [ 07/Nov/12 ] |
|
Author: {u'date': u'2012-11-06T18:37:15Z', u'email': u'andrea.lattuada@10gen.com', u'name': u'Andrea Lattuada'}Message: Signed-off-by: Andy Schwerin <schwerin@10gen.com> |
| Comment by Andrea Lattuada (Inactive) [ 06/Nov/12 ] |
|
https://github.com/mongodb/mongo/pull/321 System-wide info in ProcessInfo is currently initialized lazily because there was no support for initialization at startup time. The new code leverages MONGO_INITIALIZER* (https://jira.mongodb.org/browse/SERVER-5112) to create a single instance of ProcessInfo::SystemInfo at startup. |