determine storageEngine specificity in docs (DOCS-4856)

[DOCS-4936] FAQ 3.0 still refers to workingSet document Created: 06/Mar/15  Updated: 16/May/16  Resolved: 01/Apr/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: mongodb-3.0

Type: Sub-task Priority: Major - P3
Reporter: Andrew Ryder (Inactive) Assignee: Unassigned
Resolution: Done Votes: 1
Labels: q3-education-rotation, storage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-5560 Comment on: "manual/faq/diagnostics.t... Closed
Related
related to DOCS-5067 Comment on: "manual/reference/server-... Closed
is related to DOCS-7269 audit faq: diagnostics Closed
is related to SERVER-17731 db.serverStatus({workingSet: 1}) resu... Closed
is related to SERVER-17778 workingSet appear to not be woking in... Closed
is related to SERVER-17950 db.serverStatus() does not return rec... Closed
is related to SERVER-16378 serverStatus "indexCounters", "record... Closed
Participants:
Days since reply: 8 years, 46 weeks, 5 days ago

 Description   

RE: http://docs.mongodb.org/manual/faq/diagnostics/#what-is-working-set-and-how-can-i-estimate-its-size
(the following question is problematic too)

There is no workingSet document in 3.0 anymore. See SERVER-16378.

We need to revise this section of the FAQ to discuss how to determine memory pressure based on page-faults and other available data.



 Comments   
Comment by J Rassi [ 27/Mar/15 ]

I suggest that this also be added to the "Compatibility Changes in MongoDB 3.0" page.

Comment by Kevin Pulo [ 19/Mar/15 ]

Not only the FAQ, but also the serverStatus.workingSet reference that it links to.

Generated at Thu Feb 08 07:49:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.