[SERVER-9596] Change debug message "we think data is in ram" to a counter Created: 06/May/13  Updated: 10/Dec/14  Resolved: 13/May/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.4.3
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Tad Marshall Assignee: Tad Marshall
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All, but especially on Windows


Issue Links:
Related
related to SERVER-9623 replset9.js failing on windows Closed
related to SERVER-9658 Reduce frequency of debug message "we... Closed
Participants:

 Description   

Debug builds of mongod check to see if our internal working set tracking is accurate, and display the message "warning: we think data is in ram but system says no" when our tracking code thinks that data is in RAM but the operating system's authoritative answer is that the data is not in RAM.

We use 'QueryWorkingSetEx()' on Windows and 'mincore()' on other OSes to see if a particular page is in RAM.

On Windows, the QueryWorkingSetEx API doesn't actually tell us what is in RAM; it tells us what is in RAM and on the "Working Set" list. Pages that are in RAM and are on the 'Standby' list are not reported by this API. The result is that Windows debug builds spew large quantities of useless output, making logs hard to use.

These events should be tracked in a counter and not logged.


Generated at Thu Feb 08 03:20:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.