-
Type:
Improvement
-
Resolution: Duplicate
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 2.6.3
-
Component/s: Build
-
Fully Compatible
-
Server 2.7.4, Server 2.7.5, Server 2.7.6, BUILD 2 04/24/15
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
After compiling from source with --use-cpu-profiler, it appears that this information is not recorded in db.serverBuildInfo().complierFlags.
This info would be useful to be able to inspect the binary you are connected to and determine if its capable of cpu profiling so that profiles can be captured during a workload / run.
Example of output with a binary built with --use-cpu-profiler
> db.serverBuildInfo()
{
"version" : "2.6.3",
"gitVersion" : "255f67a66f9603c59380b2a389e386910bbb52cb",
"OpenSSLVersion" : "",
"sysInfo" : "Linux bismark 3.14-1-amd64 #1 SMP Debian 3.14.7-1 (2014-06-16) x86_64 BOOST_LIB_VERSION=1_49",
"loaderFlags" : "-fPIC -pthread -Wl,-z,now -rdynamic",
"compilerFlags" : "-Wnon-virtual-dtor -Woverloaded-virtual -fPIC -fno-strict-aliasing -ggdb -pthread -Wall -Wsign-compare -Wno-unknown-pragmas -Winvalid-pch -pipe -Werror -O3 -Wno-unused-local-typedefs -Wno-unused-function -Wno-deprecated-declarations -fno-builtin-memcmp",
"allocator" : "tcmalloc",
"versionArray" : [
2,
6,
3,
0
],
"javascriptEngine" : "V8",
"bits" : 64,
"debug" : false,
"maxBsonObjectSize" : 16777216,
"ok" : 1
}
- duplicates
-
-
- Closed
-