base on pprof is a tool for visualization and analysis of profiling data [](https://github.com/google/pprof/actions) [](https://codecov.io/gh/google/pprof) [](https://pkg.go.dev/github.com/google/pprof/profile) # Introduction pprof is a tool for visualization and analysis of profiling data. pprof reads a collection of profiling samples in profile.proto format and generates reports to visualize and help analyze the data. It can generate both text and graphical reports (through the use of the dot visualization package). profile.proto is a protocol buffer that describes a set of callstacks and symbolization information. A common usage is to represent a set of sampled callstacks from statistical profiling. The format is described on the [proto/profile.proto](./proto/profile.proto) file. For details on protocol buffers, see https://developers.google.com/protocol-buffers Profiles can be read from a local file, or over http. Multiple profiles of the same type can be aggregated or compared. If the profile samples contain machine addresses, pprof can symbolize them through the use of the native binutils tools (addr2line and nm). **This is not an official Google product.** # Building pprof Prerequisites: - Go development kit of a [supported version](https://golang.org/doc/devel/release.html#policy). Follow [these instructions](http://golang.org/doc/code.html) to prepare the environment. - Graphviz: http://www.graphviz.org/ Optional, used to generate graphic visualizations of profiles To build and install it: go install github.com/google/pprof@latest The binary will be installed `$GOPATH/bin` (`$HOME/go/bin` by default). # Basic usage pprof can read a profile from a file or directly from a server via http. Specify the profile input(s) in the command line, and use options to indicate how to format the report. ## Generate a text report of the profile, sorted by hotness: ``` % pprof -top [main_binary] profile.pb.gz Where main_binary: Local path to the main program binary, to enable symbolization profile.pb.gz: Local path to the profile in a compressed protobuf, or URL to the http service that serves a profile. ``` ## Generate a graph in an SVG file, and open it with a web browser: ``` pprof -web [main_binary] profile.pb.gz ``` ## Run pprof on interactive mode: If no output formatting option is specified, pprof runs on interactive mode, where reads the profile and accepts interactive commands for visualization and refinement of the profile. ``` pprof [main_binary] profile.pb.gz This will open a simple shell that takes pprof commands to generate reports. Type 'help' for available commands/options. ``` ## Run pprof via a web interface If the `-http` flag is specified, pprof starts a web server at the specified host:port that provides an interactive web-based interface to pprof. Host is optional, and is "localhost" by default. Port is optional, and is a random available port by default. `-http=":"` starts a server locally at a random port. ``` pprof -http=[host]:[port] [main_binary] profile.pb.gz ``` The preceding command should automatically open your web browser at the right page; if not, you can manually visit the specified port in your web browser. ## Using pprof with Linux Perf pprof can read `perf.data` files generated by the [Linux perf](https://perf.wiki.kernel.org/index.php/Main_Page) tool by using the `perf_to_profile` program from the [perf_data_converter](https://github.com/google/perf_data_converter) package. ## Viewing disassembly on Windows To view disassembly of profiles collected from Go programs compiled as Windows executables, the executable must be built with `go build -buildmode=exe`. LLVM or GCC must be installed, so required tools like `addr2line` and `nm` are available to `pprof`. ## Further documentation See [doc/README.md](doc/README.md) for more detailed end-user documentation. See [CONTRIBUTING.md](CONTRIBUTING.md) for contribution documentation. See [proto/README.md](proto/README.md) for a description of the profile.proto format. ", Assign "at most 3 tags" to the expected json: {"id":"1076","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"