package tensorflow.profiler

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message ActiveAllocation

memory_profile.proto:88

The active memory allocations at the peak memory usage.

Used in: PerAllocatorMemoryProfile

message AllReduceDbResult

steps_db.proto:59

Result database for all-reduce ops.

Used in: PerCoreStepInfo

message AllReduceInfo

steps_db.proto:41

Result proto for all -educe ops.

Used in: AllReduceDbResult

message AllReduceOpInfo

pod_viewer.proto:18

Used in: PodStatsMap

message BottleneckAnalysis

input_pipeline.proto:9

Generic hardware bottleneck.

message BufferAllocation

memory_viewer_preprocess.proto:42

Used in: PreprocessResult

message BufferSpan

memory_viewer_preprocess.proto:29

Describes the start / exclusive limit HLO program points for a given buffer lifetime, used for rendering a box on the plot.

Used in: PreprocessResult

message ChannelInfo

pod_viewer.proto:56

Next ID: 14 Information about a send and recv channel.

Used in: PodStatsMap

message CombinedTfDataStats

tf_data_stats.proto:113

TfDataStats of all hosts.

message CoreDetails

op_stats.proto:93

Next ID: 7

Used in: OpStats

message Device

trace_events.proto:23

A 'device' is a physical entity in the system and is comprised of several resources.

Used in: Trace

message DeviceCapabilities

hardware_types.proto:24

message DeviceMemoryTransfer

steps_db.proto:19

Information about memory transfer to/from device memory.

Used in: PerCoreStepInfo

message Diagnostics

diagnostics.proto:7

Used in: InputPipelineAnalysisResult, OpStats, OverviewPage, PodStatsDatabase, PodViewerDatabase

message GPUComputeCapability

hardware_types.proto:19

Used in: DeviceCapabilities

message GenericRecommendation

overview_page.proto:76

message GenericStepBreakdown

steps_db.proto:12

Breakdown of step-time on generic hardware. Note that these components are mutually exclusive so that adding them together is equal to the step time. If an execution time interval has multiple types of event happening, we need to pick one of the event type to attribute the time interval to.

message GenericStepTimeBreakdown

input_pipeline.proto:127

enum HardwareType

hardware_types.proto:8

Types of hardware profiled.

message HeapObject

memory_viewer_preprocess.proto:11

Describes a heap object that is displayed in a plot in the memory visualization HTML.

Used in: PreprocessResult

message HostDependentJobInfoResult

op_stats.proto:35

Result proto for host-dependent job information.

Used in: RunEnvironment

message HostIndependentJobInfoResult

op_stats.proto:23

Result proto for host-independent job information.

Used in: RunEnvironment

message InputOpDetails

input_pipeline.proto:97

Used in: InputPipelineAnalysisResult

message InputPipelineAnalysisRecommendation

input_pipeline.proto:117

Used in: InputPipelineAnalysisResult

message InputPipelineAnalysisResult

input_pipeline.proto:153

Used in: OverviewPage

message InputPipelineMetadata

tf_data_stats.proto:55

Metadata for input pipeline.

Used in: InputPipelineStats

enum InputPipelineMetadata.InputPipelineType

tf_data_stats.proto:60

The distribution strategy creates one "host" input pipeline which actually runs tf.data user code. Also, it creates a "device" input pipeline per device (e.g., TensorCore) which takes an element from the host input pipeline and transfers it to the device.

Used in: InputPipelineMetadata

message InputPipelineStat

tf_data_stats.proto:45

Stat and metadata for input pipeline.

Used in: InputPipelineStats

message InputPipelineStats

tf_data_stats.proto:72

Collection of metadata and stats of input pipeline.

Used in: TfDataStats

message InputTimeBreakdown

input_pipeline.proto:82

Used in: InputPipelineAnalysisResult

message IteratorMetadata

tf_data_stats.proto:29

Metadata for iterator.

Used in: TfDataStats

message IteratorStat

tf_data_stats.proto:8

Stat for iterator.

Used in: InputPipelineStat

message KernelReport

kernel_stats.proto:6

Next ID: 15

Used in: KernelStatsDb

message KernelStatsDb

kernel_stats.proto:37

Used in: OpStats

message LayoutAnalysis

op_metrics.proto:14

Data layout of an op.

Used in: OpMetrics

message LayoutAnalysis.Dimension

op_metrics.proto:16

Physical data layout in each tensor dimension.

Used in: LayoutAnalysis

enum LayoutDimensionSemantics

op_metrics.proto:6

What the dimension represents, e.g. spatial, feature or batch.

Used in: LayoutAnalysis.Dimension

message LogicalBuffer

memory_viewer_preprocess.proto:34

Used in: BufferAllocation

enum MemoryActivity

memory_profile.proto:7

The memory activity that causes change of memory state.

Used in: MemoryActivityMetadata

message MemoryActivityMetadata

memory_profile.proto:38

The metadata associated with each memory allocation/deallocation. It can also be interpreted as the metadata for the delta of memory state. Next ID: 10

Used in: MemoryProfileSnapshot, PerAllocatorMemoryProfile

message MemoryAggregationStats

memory_profile.proto:21

The aggregated memory stats including heap, stack, free memory and fragmentation at a specific time.

Used in: MemoryProfileSnapshot, MemoryProfileSummary

message MemoryProfile

memory_profile.proto:118

Data for memory usage analysis in one host.

message MemoryProfileSnapshot

memory_profile.proto:65

Profile snapshot of the TensorFlow memory at runtime, including MemoryAggregationStats (memory usage breakdown etc.), and MemoryActivityMetadata (allocation or deallocation, TF Op name etc.).

Used in: PerAllocatorMemoryProfile

message MemoryProfileSummary

memory_profile.proto:75

The summary of memory profile within the profiling window duration.

Used in: PerAllocatorMemoryProfile

message OpMetrics

op_metrics.proto:30

Metrics for an operation (accumulated over all occurrences). Next ID: 24

Used in: OpMetricsDb

message OpMetrics.MemoryAccessed

op_metrics.proto:56

Breakdown of memory accessed by operation type and memory space.

Used in: OpMetrics

enum OpMetrics.MemoryAccessed.OperationType

op_metrics.proto:57

Used in: MemoryAccessed

message OpMetricsDb

op_metrics.proto:97

A database for OpMetrics. Next ID: 14

Used in: OpMetrics, OpStats, PerCoreStepInfo

message OpStats

op_stats.proto:110

Next ID: 14 Operator Statistics.

message OverviewPage

overview_page.proto:191

message OverviewPageAnalysis

overview_page.proto:30

Overview result for general analysis.

Used in: OverviewPage

message OverviewPageHostDependentJobInfo

overview_page.proto:150

Result proto for host-dependent job information.

Used in: OverviewPageRunEnvironment

message OverviewPageHostIndependentJobInfo

overview_page.proto:138

Result proto for host-independent job information.

Used in: OverviewPageRunEnvironment

message OverviewPageRecommendation

overview_page.proto:101

Overview result for the recommendation section.

Used in: OverviewPage

message OverviewPageRunEnvironment

overview_page.proto:164

The run environment of a profiling session.

Used in: OverviewPage

message OverviewPageTip

overview_page.proto:71

Overview result for a performance tip to users.

Used in: OverviewPageRecommendation

message OverviewTfOp

overview_page.proto:10

Overview result for a TensorFlow Op.

Used in: OverviewPageAnalysis

message PerAllocatorMemoryProfile

memory_profile.proto:99

Memory profile snapshots per memory allocator.

Used in: MemoryProfile

message PerCoreStepInfo

steps_db.proto:64

Result proto for information in a step across all cores.

Used in: StepDatabaseResult

message PerGenericStepDetails

input_pipeline.proto:50

Per-step details on generic hardware.

message PerfEnv

op_stats.proto:12

Performance environment, e.g the peak performance capabilities of the device.

Used in: OpStats

message PerformanceCounterResult

op_stats.proto:103

Metrics based on hardware performance counters.

Used in: OpStats

message PodStatsDatabase

pod_stats.proto:13

A database of PodStats records.

message PodStatsMap

pod_viewer.proto:35

Result proto for information in a step across all cores.

Used in: PodStatsSequence

message PodStatsRecord

pod_stats.proto:25

Next ID: 20 There is one PodStatsRecord for each step traced on each compute node.

Used in: PodStatsDatabase, PodStatsMap

message PodStatsSequence

pod_viewer.proto:50

A sequence of PodStatsMap for each step.

Used in: PodViewerDatabase

message PodViewerDatabase

pod_viewer.proto:110

Next ID: 12 A database of pod viewer records.

message PodViewerSummary

pod_viewer.proto:84

Used in: PodViewerDatabase

message PodViewerTopology

pod_viewer.proto:91

Next ID: 8 Topology graph draws all the cores in the system in a 2-D rectangle or 3-D cube. It is hierarchically grouped by host, chip and core.

Used in: PodViewerDatabase

message PrecisionStats

op_metrics.proto:88

Statistics about the various precision used in computation.

Used in: OpMetricsDb

message PreprocessResult

memory_viewer_preprocess.proto:51

Groups together all results from the preprocessing C++ step.

message ReplicaGroup

pod_viewer.proto:12

Describes the replica groups in a cross replica op (e.g., all-reduce and all-to-all).

Used in: AllReduceOpInfo

message Resource

trace_events.proto:37

A 'resource' generally is a specific computation component on a device. These can range from threads on CPUs to specific arithmetic units on hardware devices.

Used in: Device

message RunEnvironment

op_stats.proto:61

The run environment of a profiling session.

Used in: OpStats

message StepBreakdownEvents

pod_stats.proto:7

Used in: PodStatsDatabase, PodViewerDatabase

message StepDatabaseResult

steps_db.proto:87

Result proto for a StepDatabase.

Used in: OpStats

message StepInfoResult

steps_db.proto:27

Next ID: 6 Result proto for StepInfo.

Used in: PerCoreStepInfo

message StepSummary

input_pipeline.proto:42

Used for both step duration and Op duration.

Used in: GenericStepTimeBreakdown, InputPipelineAnalysisResult

message SystemTopology

op_stats.proto:50

System topology, which describes the number of chips in a pod and the connectivity style.

Used in: RunEnvironment

message TfDataBottleneckAnalysis

tf_data_stats.proto:95

Used in: CombinedTfDataStats

message TfDataStats

tf_data_stats.proto:88

Collection of stats of tf.data input pipelines within a host.

Used in: CombinedTfDataStats

message TfFunction

tf_function.proto:44

Statistics for a tf-function.

Used in: TfFunctionDb

enum TfFunctionCompiler

tf_function.proto:21

All possible compilers that can be used to compile a tf-function in the graph mode.

Used in: TfFunction

message TfFunctionDb

tf_function.proto:58

Statistics for all tf-functions.

Used in: OpStats

enum TfFunctionExecutionMode

tf_function.proto:6

All possible execution modes of a tf-function.

message TfFunctionMetrics

tf_function.proto:36

Metrics associated with a particular execution mode of a tf-function.

Used in: TfFunction

message TfStatsDatabase

tf_stats.proto:8

A database of TfStatsTables.

message TfStatsRecord

tf_stats.proto:29

There is one TfStatsRecord for each TF operation profiled.

Used in: TfStatsTable

message TfStatsTable

tf_stats.proto:19

A table of TFStatsRecords plus the corresponding pprof keys.

Used in: TfStatsDatabase

message Trace

trace_events.proto:12

A 'Trace' contains metadata for the individual traces of a system.

message TraceEvent

trace_events.proto:49

Used in: Trace

message XEvent

xplane.proto:78

An XEvent is a trace event, optionally annotated with XStats. Next ID: 6

Used in: XLine

message XEventMetadata

xplane.proto:122

Metadata for an XEvent, corresponds to an event type and is shared by all XEvents with the same metadata_id. Next ID: 7

Used in: XPlane

message XLine

xplane.proto:47

An XLine is a timeline of trace events (XEvents). Next ID: 12

Used in: XPlane

message XPlane

xplane.proto:22

An XPlane is a container of parallel timelines (XLines), generated by a profiling source or by post-processing one or more XPlanes. Next ID: 7

Used in: XSpace

message XSpace

xplane.proto:9

A container of parallel XPlanes, generated by one or more profiling sources. Next ID: 5

message XStat

xplane.proto:103

An XStat is a named value associated with an XEvent, e.g., a performance counter value, a metric computed by a formula applied over nested XEvents and XStats. Next ID: 8

Used in: XEvent, XEventMetadata, XPlane

message XStatMetadata

xplane.proto:146

Metadata for an XStat, corresponds to a stat type and is shared by all XStats with the same metadata_id. Next ID: 4

Used in: XPlane