aboutsummaryrefslogtreecommitdiffhomepage
path: root/tensorflow/core/profiler/g3doc/options.md
diff options
context:
space:
mode:
authorGravatar A. Unique TensorFlower <gardener@tensorflow.org>2017-11-30 15:20:30 -0800
committerGravatar TensorFlower Gardener <gardener@tensorflow.org>2017-11-30 15:23:54 -0800
commitce4200eae990d7f5efdfb727939d38bf48001ba2 (patch)
tree7c9c3e9cd932273198fa2ef8e4fb24637de1f42f /tensorflow/core/profiler/g3doc/options.md
parent6bfc73a0b3c6810725a5eb0020470457cc5cc23e (diff)
Fix profiler to track some missed persistent bytes.
PiperOrigin-RevId: 177516249
Diffstat (limited to 'tensorflow/core/profiler/g3doc/options.md')
-rw-r--r--tensorflow/core/profiler/g3doc/options.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/tensorflow/core/profiler/g3doc/options.md b/tensorflow/core/profiler/g3doc/options.md
index 4c73e372e3..dd12f76d6f 100644
--- a/tensorflow/core/profiler/g3doc/options.md
+++ b/tensorflow/core/profiler/g3doc/options.md
@@ -60,11 +60,14 @@ Currently, profiler only tracks the allocation of memory. As a result, the
accumulated memory request is uaually larger than the peak memory of the overall
model.
-bytes: The memory allocations requested by the operation.
-peak_bytes: The peak requested memory (not de-allocated) by the operation.
-residual_bytes: The memory requested by the operation and not de-allocated
+It's recommended to generate timeline to see the allocator memory usage over
+time.
+
+`bytes`: The memory allocations requested by the operation.
+`peak_bytes`: The peak requested memory (not de-allocated) by the operation.
+`residual_bytes`: The memory requested by the operation and not de-allocated
when Compute finishes.
-output_bytes: The memory output by the operation. It's not necessarily requested
+`output_bytes`: The memory output by the operation. It's not necessarily requested
by the current operation. For example, it can be a tensor
forwarded from input to output, with in-place mutation.