multi: separate profiler config

sample-lnd.conf

@@ -266,28 +266,32 @@
 ; Example:
 ;   debuglevel=debug,PEER=info
 
-; Write CPU profile to the specified file.
+; DEPRECATED: Use pprof.cpuprofile instead. Write CPU profile to the specified 
+; file.
 ; cpuprofile=
 
-; Enable HTTP profiling on given port -- NOTE port must be between 1024 and
-; 65536. The profile can be access at: http://localhost:<PORT>/debug/pprof/.
-; You can also provide it as host:port to enable profiling for remote debugging.
-; For example 0.0.0.0:<PORT> to enable profiling for all interfaces on the given
-; port.
+; DEPRECATED: Use pprof.profile instead.Enable HTTP profiling on given port 
+; -- NOTE port must be between 1024 and 65536. The profile can be access at:
+; http://localhost:<PORT>/debug/pprof/. You can also provide it as host:port to
+; enable profiling for remote debugging. For example 0.0.0.0:<PORT> to enable
+; profiling for all interfaces on the given port.
 ; profile=
 
-; Enable a blocking profile to be obtained from the profiling port. A blocking
-; profile can show where goroutines are blocking (stuck on mutexes, I/O, etc).
-; This takes a value from 0 to 1, with 0 turning off the setting, and 1 sampling
-; every blocking event (it's a rate value).
+; DEPRECATED: Use pprof.blockingprofile instead. Enable a blocking profile to be
+; obtained from the profiling port. A blocking profile can show where goroutines
+; are blocking (stuck on mutexes, I/O, etc). This takes a value from 0 to 1,
+; with 0 turning off the setting, and 1 sampling every blocking event (it's a
+; rate value).
 ; blockingprofile=0
 
-; Enable a mutex profile to be obtained from the profiling port. A mutex 
-; profile can show where goroutines are blocked on mutexes, and which mutexes
-; have high contention.  This takes a value from 0 to 1, with 0 turning off the
-; setting, and 1 sampling every mutex event (it's a rate value).
+; DEPRECATED: Use pprof.mutexprofile instead. Enable a mutex profile to be 
+; obtained from the profiling port. A mutex profile can show where goroutines 
+; are blocked on mutexes, and which mutexes have high contention. This takes a
+; value from 0 to 1, with 0 turning off the setting, and 1 sampling every mutex
+; event (it's a rate value).
 ; mutexprofile=0
 
+
 ; DEPRECATED: Allows the rpcserver to intentionally disconnect from peers with
 ; open channels. THIS FLAG WILL BE REMOVED IN 0.10.0.
 ; unsafe-disconnect=false
@@ -1814,3 +1818,35 @@
 ; no active gRPC streams. This might be useful to keep the underlying HTTP/2
 ; connection open for future requests.
 ; grpc.client-allow-ping-without-stream=false
+
+
+[pprof]
+
+; Enable HTTP profiling on given port -- NOTE port must be between 1024 and
+; 65536. The profile can be access at: http://localhost:<PORT>/debug/pprof/.
+; You can also provide it as host:port to enable profiling for remote debugging.
+; For example 0.0.0.0:<PORT> to enable profiling for all interfaces on the given
+; port. The built-in profiler has minimal overhead, so it is recommended to
+; enable it.
+; pprof.profile=
+
+; Write CPU profile to the specified file. This should only be used for 
+; debugging because compared to running a pprof server this will record the cpu
+; profile constantly from the start of the program until the shutdown.
+; pprof.cpuprofile=
+
+; Enable a blocking profile to be obtained from the profiling port. A blocking
+; profile can show where goroutines are blocking (stuck on mutexes, I/O, etc).
+; This takes a value from 0 to 1, with 0 turning off the setting, and 1 sampling
+; every blocking event (it's a rate value). The blocking profile has high 
+; overhead and is off by default even when running the pprof server. It should
+; only be used for debugging.
+; pprof.blockingprofile=0
+
+; Enable a mutex profile to be obtained from the profiling port. A mutex 
+; profile can show where goroutines are blocked on mutexes, and which mutexes
+; have high contention.  This takes a value from 0 to 1, with 0 turning off the
+; setting, and 1 sampling every mutex event (it's a rate value). The mutex
+; profile has high overhead and is off by default even when running the pprof
+; server. It should only be used for debugging.
+; pprof.mutexprofile=0