[SERVER-8484] workingSet command pagesInMemory estimate not affected by db "touch" command Created: 08/Feb/13 Updated: 15/Feb/13 Resolved: 09/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
After a server restart, pagesInMemory is low (as expected) but then using "touch" command to try forcing the collection into ram, it only increments by one. The data set used for testing was ~1.4gb.
|
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 09/Feb/13 ] |
|
This behavior is correct. |
| Comment by Eric Milkie [ 08/Feb/13 ] |
|
I believe the logic for determining when PageFaultException is thrown uses more information than just the PointerTable, although such information is not entirely accurate on Windows. |
| Comment by Eric Milkie [ 08/Feb/13 ] |
|
I think this is because the touch command bypasses the way we are tracking working set pages, which is a hook in the record accessing functions. |