rust/greptimedb
1
0
Fork 0
mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-05-20 15:00:40 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
7efff2d704991e32cbdeebd8047c002962893e43
greptimedb/src/common/mem-prof
History
shuiyisong 7efff2d704 fix: introduce taplo.toml and sort Cargo.toml (#2096) 
* fix: add taplo.toml

* fix: introduce taplo.toml & sort cargo.toml

* chore: remove option in ci too
2023-08-04 06:44:45 +00:00
..
src
refactor:remove common_error::prelude (#1946)
2023-07-13 10:36:36 +08:00
Cargo.toml
fix: introduce taplo.toml and sort Cargo.toml (#2096)
2023-08-04 06:44:45 +00:00
README.md
feat: memory profiling (#1124)
2023-03-07 17:12:51 +08:00

README.md

Profile memory usage of GreptimeDB

This crate provides an easy approach to dump memory profiling info.

Prerequisites

jemalloc

# for macOS
brew install jemalloc

# for Ubuntu
sudo apt install libjemalloc-dev

flamegraph

curl https://raw.githubusercontent.com/brendangregg/FlameGraph/master/flamegraph.pl > ./flamegraph.pl

Build GreptimeDB with mem-prof feature.

cargo build --features=mem-prof

Profiling

Start GreptimeDB instance with environment variables:

MALLOC_CONF=prof:true,lg_prof_interval:28 ./target/debug/greptime standalone start

Dump memory profiling data through HTTP API:

curl localhost:4000/v1/prof/mem > greptime.hprof

You can periodically dump profiling data and compare them to find the delta memory usage.

Analyze profiling data with flamegraph

To create flamegraph according to dumped profiling data:

jeprof --svg <path_to_greptimedb_binary> --base=<baseline_prof> <profile_data> > output.svg