package tensorflow.profiler

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

message AllReduceDbResult

steps_db.proto:76

Result database for all-reduce ops.

Used in: PerCoreStepInfo

message AllReduceInfo

steps_db.proto:58

Result proto for all -educe ops.

Used in: AllReduceDbResult

message CudaComputeCapability

hardware_types.proto:19

Used in: DeviceCapabilities

message Device

trace_events.proto:22

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 FlowDbResult

steps_db.proto:53

Result database for core to core flow events.

Used in: PerCoreStepInfo

message FlowEventInfo

steps_db.proto:32

Result proto for metrics on flow events.

Used in: FlowDbResult

message GenericRecommendation

overview_page.proto:50

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:85

enum HardwareType

hardware_types.proto:8

Types of hardware profiled.

Used in: InputPipelineAnalysisResult

message HostDependentJobInfoResult

op_stats.proto:32

Result proto for host-dependent job information.

Used in: RunEnvironment

message HostIndependentJobInfoResult

op_stats.proto:20

Result proto for host-independent job information.

Used in: RunEnvironment

message InputOpDetails

input_pipeline.proto:60

Used in: InputPipelineAnalysisResult

message InputPipelineAnalysisRecommendation

input_pipeline.proto:80

Used in: InputPipelineAnalysisResult

message InputPipelineAnalysisResult

input_pipeline.proto:109

Used in: OverviewPage

message InputTimeBreakdown

input_pipeline.proto:45

Used in: InputPipelineAnalysisResult

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 OpMetrics

op_metrics.proto:30

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

Used in: OpMetricsDb

message OpMetricsDb

op_metrics.proto:65

A database for OpMetrics. Next ID: 13

Used in: OpMetrics, OpStats, PerCoreStepInfo

message OpStats

op_stats.proto:89

Operator Statistics.

message OverviewPage

overview_page.proto:87

message OverviewPageAnalysis

overview_page.proto:25

Overview result for general analysis.

Used in: OverviewPage

message OverviewPageRecommendation

overview_page.proto:66

Overview result for the recommendation section.

Used in: OverviewPage

message OverviewPageTip

overview_page.proto:45

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 PerCoreStepInfo

steps_db.proto:81

Result proto for information in a step across all cores.

Used in: StepDatabaseResult

message PerGenericStepDetails

input_pipeline.proto:17

Per-step details on generic hardware.

message PerfEnv

op_stats.proto:9

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

Used in: OpStats

message Resource

trace_events.proto:36

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:58

The run environment of a profiling session.

Used in: OpStats, OverviewPage

message StepDatabaseResult

steps_db.proto:98

Result proto for a StepDatabase.

Used in: OpStats

message StepInfoResult

steps_db.proto:20

Next ID: 5 Result proto for StepInfo.

Used in: PerCoreStepInfo

message StepSummary

input_pipeline.proto:9

Used for both step duration and Op duration.

Used in: GenericStepTimeBreakdown, InputPipelineAnalysisResult

message SystemTopology

op_stats.proto:47

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

Used in: RunEnvironment

message TfStatsDatabase

tf_stats.proto:8

A database of TfStatsTables.

message TfStatsRecord

tf_stats.proto:27

There is one TfStatsRecord for each TF operation profiled.

Used in: TfStatsTable

message TfStatsTable

tf_stats.proto:17

A table of TFStatsRecords plus the corresponding pprof keys.

Used in: TfStatsDatabase

message Trace

trace_events.proto:11

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

message TraceEvent

trace_events.proto:44

Used in: Trace

message XEvent

xplane.proto:71

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

Used in: XLine

message XEventMetadata

xplane.proto:110

Metadata for an XEvent, shared by all instances of the same event. Next ID: 5

Used in: XPlane

message XLine

xplane.proto:40

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

Used in: XPlane

message XPlane

xplane.proto:16

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: 2

message XStat

xplane.proto:95

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: 6

Used in: XEvent, XPlane

message XStatMetadata

xplane.proto:126

Metadata for an XStat, shared by all instances of the same stat. Next ID: 4

Used in: XPlane