From f0896a94c5e628844f89090da9c76fee0b051c9f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Sun, 17 Jan 2021 19:33:55 +0100 Subject: [PATCH] Add some disclaimers --- cpu.md | 4 ++++ pprof.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/cpu.md b/cpu.md index bd2bee5..27c78d9 100644 --- a/cpu.md +++ b/cpu.md @@ -75,3 +75,7 @@ The various ways one can record CPU profiles in Go are listed below. - bias - performance overhead - Discuss [Proposal: hardware performance counters for CPU profiling.](https://go.googlesource.com/proposal/+/refs/changes/08/219508/2/design/36821-perf-counter-pprof.md) + +## Disclaimer + +I've just started a new job at [Datadog](https://www.datadoghq.com/) to work on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. This document may not reflect the views of my employer, but they were kind enough to let me publish it : ). diff --git a/pprof.md b/pprof.md index 3a23af2..7ed5f0e 100644 --- a/pprof.md +++ b/pprof.md @@ -151,3 +151,7 @@ The output above is truncated also, [pprof.samples.cpu.001.protoc.txt](./example - Explain why pprof can be given a path to the binary the profile belongs to. - Get into more details about line numbers / addresses. - Talk about mappings and when a Go binary might have more than one + +## Disclaimer + +I've just started a new job at [Datadog](https://www.datadoghq.com/) to work on [Continuous Profiling](https://www.datadoghq.com/product/code-profiling/) for Go. This document may not reflect the views of my employer, but they were kind enough to let me publish it : ).