[SERVER-14682] --use-cpu-profiler does not appear to be recorded in db.serverBuildInfo() Created: 25/Jul/14  Updated: 17/Apr/15  Resolved: 17/Apr/15

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: 2.6.3
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Alvin Richards (Inactive) Assignee: Jonathan Reams
Resolution: Duplicate Votes: 0
Labels: community-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File profiler.diff    
Issue Links:
Depends
Duplicate
duplicates SERVER-18099 Refactor buildinfo Closed
Backwards Compatibility: Fully Compatible
Sprint: Server 2.7.4, Server 2.7.5, Server 2.7.6, BUILD 2 04/24/15
Participants:

 Description   

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
}



 Comments   
Comment by Jonathan Reams [ 17/Apr/15 ]

This will be done in SERVER-18099

Generated at Thu Feb 08 03:35:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.