[DOCS-3212] Description of "page fault" in mongostat and other places not totally clear Created: 18/Apr/14 Updated: 21/Jul/14 Resolved: 09/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Buzz Moschetti | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint-rollover | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 30 weeks, 2 days ago | ||||||||
| Description |
|
The description of page fault as observed in mongostat and in serverStatus is not 100% clear and often leads O/S oriented people to misinterpret the meaning. The docs glossary def inition of page fault is even less appropriate for the mongoDB meaning. The description everywhere should always compare and contrast our page fault def to the more tradition def so that it is very very clear that our page faults do not necessarily imply a yellow flag for poor system performance or configuration. The def should look something like this: page_fault: |
| Comments |
| Comment by Githook User [ 21/Jul/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Tim Slavin [ 10/Jul/14 ] |
|
FYI does it matter this is Fixed but still open in Github? On Wed, Jul 9, 2014 at 6:15 PM, Sam Kleinman (JIRA) <jira@mongodb.org> |