- 
    Type:New Feature 
- 
    Resolution: Unresolved
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: Performance
- 
        Query Optimization
- 
        (copied to CRM)
- 
        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.
- is depended on by
- 
                    SERVER-5266 Make a clearer API for configuring global slowms -         
- Backlog
 
-         
- is related to
- 
                    SERVER-18946 I wish I can configure separately the profiler and log file -         
- Open
 
-         
- related to
- 
                    SERVER-11125 setProfilingLevel() does not accept zero for slowms parameter -         
- Closed
 
-         
- 
                    SERVER-4786 Random sampling for profiling and logging -         
- Closed
 
-         
- links to