MINOR: activity: add a "memory" entry to "profiling"
This adds the necessary flags to permit run-time enabling/disabling of
memory profiling. For now this is disabled.
A few words were added to the management doc about it and recalling that
this is limited to certain OSes.
diff --git a/doc/management.txt b/doc/management.txt
index bba88c0..a16a86d 100644
--- a/doc/management.txt
+++ b/doc/management.txt
@@ -1917,12 +1917,15 @@
delayed until the threshold is reached. A value of zero restores the initial
setting.
-set profiling { tasks } { auto | on | off }
- Enables or disables CPU profiling for the indicated subsystem. This is
- equivalent to setting or clearing the "profiling" settings in the "global"
+set profiling { tasks | memory } { auto | on | off }
+ Enables or disables CPU or memory profiling for the indicated subsystem. This
+ is equivalent to setting or clearing the "profiling" settings in the "global"
section of the configuration file. Please also see "show profiling". Note
that manually setting the tasks profiling to "on" automatically resets the
scheduler statistics, thus allows to check activity over a given interval.
+ The memory profiling is limited to certain operating systems (known to work
+ on the linux-glibc target), and requires USE_MEMORY_PROFILING to be set at
+ compile time.
set rate-limit connections global <value>
Change the process-wide connection rate limit, which is set by the global