From f6ace4dd83f962d3a8a569e21820b454e9683013 Mon Sep 17 00:00:00 2001
From: gmarek <gmarek@google.com>
Date: Thu, 19 Feb 2015 14:50:54 +0100
Subject: [PATCH] Add info about contention profiling to profiling.md

---
 docs/devel/profiling.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/devel/profiling.md b/docs/devel/profiling.md
index 68d1cc242ed..142ef11e54e 100644
--- a/docs/devel/profiling.md
+++ b/docs/devel/profiling.md
@@ -23,8 +23,12 @@ Even when running profiler I found not really straightforward to use 'go tool pp
 ```
   ssh kubernetes_master -L<local_port>:localhost:8080
 ```
-or analogous one for you Cloud provider. Afterwards you can e.g. run 
+or analogous one for you Cloud provider. Afterwards you can e.g. run
 ```
 go tool pprof http://localhost:<local_port>/debug/pprof/profile
 ```
 to get 30 sec. CPU profile.
+
+## Contention profiling
+
+To enable contetion profiling you need to add line ```rt.SetBlockProfileRate(1)``` to ones added before (```rt``` stands for ```runtime``` in ```master.go```). This enables 'debug/pprof/block' subpage, which can be used as an input go to ```go tool pprof```.