From c972bee3af8bf38b2cd8f61224a5fe41f662e6f7 Mon Sep 17 00:00:00 2001 From: Allison Moore Date: Tue, 30 Dec 2014 11:57:07 -0500 Subject: [PATCH] DOCS-4447: updates profiler for WT changes - notes that numYield and lockStats are not output for WT databases --- source/reference/database-profiler.txt | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/source/reference/database-profiler.txt b/source/reference/database-profiler.txt index 14964a2f8c4..383774e411a 100644 --- a/source/reference/database-profiler.txt +++ b/source/reference/database-profiler.txt @@ -207,7 +207,14 @@ operation. data that MongoDB has not yet fully read into memory. This allows other operations that have data in memory to complete while MongoDB reads in data for the yielding operation. For more information, - see :ref:`the FAQ on when operations yield `. + see :ref:`the FAQ on when operations yield + `. + + .. versionchanged:: 2.8.0 + :data:`system.profile.numYeild` does not apply to databases + using the :doc:`WiredTiger ` storage engine, and + as such, is not included in the profiler output for + those databases. .. data:: system.profile.lockStats @@ -233,6 +240,12 @@ operation. The time in microseconds the operation spent waiting to acquire a specific lock. + + .. versionchanged:: 2.8.0 + :data:`system.profile.lockStats` does not apply to databases + using the :doc:`WiredTiger ` storage engine, and + as such, is not included in the profiler output for + those databases. .. data:: system.profile.nreturned