| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
reporting.
This change applies to various server diagnostics which
include latency metrics: the slow query logs, the
system.profile collection, top, global operation latency
stats, and per-collection operation latency stats. The
secs_running and microsecs_running fields reported in
currentOp output, on the other hand, will include time spent
blocking for awaitData.
Furthermore, this change fixes the following:
- getMore operations are no longer double-counted.
- Lock acquisition times are now consistently included.
This fixes a bug in which time spent acquiring locks was
accidentally omitted in some cases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Presently it directly calls `assembleResponse`, which is responsible
for a cyclic dependency. This functionality is available through
the `ServiceContext` mechanism, and thus needn't directly use
`assembleResponse`.
The `ServiceEntryPoint` member of `ServiceContext` is set through
a setter, which isn't always called, so we initialize the global
entry through a factory function.
This also removes the superfluous argument for `HostAndPort`, as
that was used to track whether the call was made from within the
`DbDirectClient` object itself or from the network -- a separate
bit in the `OperationContext` indicates that state.
|
| |
|
| |
|
|
|
|
|
|
| |
Putting `CursorManager` and `ClientCursor` in the same library
allows us to remove a cycle exemption in cursor and to fully
resolve mmap_v1 against dependencies.
|
|
|
|
| |
dispatch
|
|
|
|
| |
update/delete
|
| |
|
| |
|
| |
|
|
|
|
| |
collections are unsharded
|
| |
|
|
|
|
|
| |
It is been deprecated since at least 1.2 and was never supported in mongos.
Deleting to make room for the new OP_MSG format.
|
|
|
|
|
|
| |
This commit is an automated rename of all whole word instances of txn,
_txn, and txnPtr to opCtx, _opCtx, and opCtxPtr, respectively in all
.cpp and .h files in src/mongo.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a sampleRate parameter to the profile command, a value
on the interval [0, 1] which indicates which fraction of
operations should be randomly sampled for profiling and
logging. This allows users to reduce their slowms threshold
or increase their profiling level with less performance
impact on the system.
Closes #1099
Signed-off-by: David Storch <david.storch@10gen.com>
|
|
|