Skip to content

DOCS-4447: updates profiler for WT changes #2094

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion source/reference/database-profiler.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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 <faq-concurrency-yielding>`.
see :ref:`the FAQ on when operations yield
<faq-concurrency-yielding>`.

.. versionchanged:: 2.8.0
:data:`system.profile.numYeild` does not apply to databases
using the :doc:`WiredTiger </core/storage>` storage engine, and
as such, is not included in the profiler output for
those databases.

.. data:: system.profile.lockStats

Expand All @@ -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 </core/storage>` storage engine, and
as such, is not included in the profiler output for
those databases.

.. data:: system.profile.nreturned

Expand Down