slowms should be per database for profiler

XMLWordPrintableJSON

    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The slowms constant is not per database but is process wide.

      > db.setProfilingLevel(1,1000)
{ "was" : 0, "slowms" : 100, "ok" : 1 }
> db.getProfilingStatus()
{ "was" : 1, "slowms" : 1000 }
> use test2
switched to db test2
> db.setProfilingLevel(1,2)
{ "was" : 0, "slowms" : 1000, "ok" : 1 }
> db.getProfilingStatus()
{ "was" : 1, "slowms" : 2 }
> use test
switched to db test
> db.getProfilingStatus()
{ "was" : 1, "slowms" : 2 }

      Notice how slowms went to 2 in the test database... That is not good.

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: