[SERVER-3910] millis always 0 when profilingLevel is 2 Created: 20/Sep/11 Updated: 11/Jul/16 Resolved: 03/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | 2.0.1, 2.1.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Daniel Crosta | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | OS X |
| Participants: |
| Description |
|
I've created a collection with 100k entries like:
And query with:
Explain shows this:
But system.profile shows this:
With profiling level set to 1, the output in system.profile reflects the correct millis. The profile output in 1.8.3 is correct:
(Note that this behavior is true with or without .explain(), I only used that to find out the actual millis to execute the query) |
| Comments |
| Comment by auto [ 03/Oct/11 ] | ||
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: setProfilingLevel(2) not always working because millis set in wrong place | ||
| Comment by auto [ 03/Oct/11 ] | ||
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: test for | ||
| Comment by auto [ 03/Oct/11 ] | ||
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: setProfilingLevel(2) not always working because millis set in wrong place | ||
| Comment by Daniel Crosta [ 20/Sep/11 ] | ||
|
Workaround: Rather than:
use:
Then the correct millis is reported in system.profile. |