include/mempool: note about runtime complexity

Signed-off-by: Sage Weil <sage@redhat.com>

diff --git a/src/include/mempool.h b/src/include/mempool.h
index 029915417054a892d3b0e2bff42a70e44b459fc3..74fdc15193036847eab79571c2cb24328a603d39 100644 (file)
--- a/src/include/mempool.h
+++ b/src/include/mempool.h
@@ -148,13 +148,17 @@ The simplest way to interrogate the process is with
   Formater *f = ...
   mempool::dump(f);
 
-This will dump information about *all* memory pools.
+This will dump information about *all* memory pools.  When debug mode
+is enabled, the runtime complexity of dump is O(num_shards *
+num_types).  When debug name is disabled it is O(num_shards).
 
 You can also interogate a specific pool programatically with
 
   size_t bytes = unittest_2::allocated_bytes();
   size_t items = unittest_2::allocated_items();
 
+The runtime complexity is O(num_shards).
+
 Note that you cannot easily query per-type, primarily because debug
 mode is optional and you should not rely on that information being
 available.