From 6681b6c069ea4d866adb39fec85ddcc37956777f Mon Sep 17 00:00:00 2001 From: Jimmy99 Date: Wed, 6 Apr 2016 21:36:16 +0200 Subject: [PATCH] Update 14.6.md Typographical errors and improved readability --- en/14.6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/14.6.md b/en/14.6.md index 9ce86123..5ad61fc9 100644 --- a/en/14.6.md +++ b/en/14.6.md @@ -10,7 +10,7 @@ In fact, `net/http/pprof` simply exposes runtime profiling data from the `runtim ## pprof support in Beego -The Beego framework currently supports pprof, however it is not not turned on by default. If you need to test the performance of your application, (for instance by viewing the execution goroutine such information, in fact, Go's default package "net/http/pprof" already has this feature, and if Go manner in accordance with the default Web, you can use the default, but because beego repackaged ServHTTP function, so if you can not open the default includes this feature, so the need for internal reform beego support pprof. +The Beego framework currently supports pprof, however it is not not turned on by default. If you need to test the performance of your application, (for instance by viewing the execution goroutine) such information from Go's default package "net/http/pprof" already has this feature. Because beego has repackaged the ServHTTP function, you can not open the default feature included in pprof. This resulted in beego supporting pprof internally. - First in our `beego.Run` function, we choose whether or not to automatically load the performance pack according to our configuration variable (in this case, PprofOn):