Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

XProf (+ Tensorboard Profiler Plugin)

An open, scalable, and extensible profiler for the modern ML stack.

AboutInstallationUsageResourcesCiting

Badge to display Apache 2.0 license Badge to display current XProf version Badge to display weekly PyPi downloads

About

XProf offers a number of tools to analyse and visualize the performance of your model across multiple devices. Some of the tools include:

Overview Page

A high-level overview of the performance of your model. This is an aggregated overview for your host and all devices. It includes:
  • Performance summary and breakdown of step times.
  • A graph of individual step times.
  • High level details of the run environment.

Trace Viewer

Displays a timeline of the execution of your model that shows:
  • The duration of each op.
  • Which part of the system (host or device) executed an op.
  • The communication between devices.

Memory Profile

Monitors the memory usage of your model.

Graph Viewer

A visualization of the graph structure of HLOs of your model.

To learn more about the various XProf tools, check out the XProf documentation

[!TIP] New to profiling? Come and check out this Colab Demo.

Installation

To get the most recent release version of XProf, install it via pip:

$ pip install xprof

[!NOTE] For Python 3.12+ users, if you encounter ModuleNotFoundError: No module named 'pkg_resources', install an older version of setuptools:

pip install "setuptools<70"

Alternative installation options:

Installation with Tensorboard
$ pip install xprof tensorboard
Google Cloud

If you use Google Cloud to run your workloads, we recommend the xprofiler tool.It provides a streamlined profile collection and viewing experience using VMs running XProf.

Nightly Releases

Every night, a nightly version of the package is released under the name of xprof-nightly. This package contains the latest changes made by the XProf developers.

To install the nightly version of profiler:

$ pip uninstall xprof tensorboard-plugin-profile
$ pip install xprof-nightly
Build from Source

If the pip packages don't work, you can build XProf from source using Bazel.

1. Set up Bazel

Bazel is the build system used for XProf. Bazelisk is a wrapper for Bazel that simplifies Bazel version management. Download the appropriate .deb package for your system from the Bazelisk releases page and install the downloaded package:

sudo apt install ~/Downloads/bazelisk-amd64.deb

2. Obtain the Repository

Clone the XProf GitHub repository to your local machine:

git clone https://github.com/openxla/xprof.git
cd xprof

3. Build the Project

Build the pip Package: Use Bazel to build the XProf pip package:

bazel run --config=public_cache plugin:build_pip_package

Navigate to the Bazel Output Directory and install:

cd /tmp/profile-pip
pip install .

Usage

[!IMPORTANT] XProf requires access to the Internet to load the Google Chart library. Some charts and tables may be missing if you run XProf entirely offline on your local machine, behind a corporate firewall, or in a datacenter.

Standalone

If you have profile data in a directory (e.g., profiler/demo), you can view it by running:

$ xprof --logdir=profiler/demo --port=6006

Or with the optional command name:

$ xprof server --logdir=profiler/demo --port=6006

With TensorBoard

If you have TensorBoard installed, you can run:

$ tensorboard --logdir=profiler/demo

If you are behind a corporate firewall, you may need to include the --bind_all tensorboard flag.

Go to localhost:6006/#profile of your browser, you should now see the demo overview page show up. Congratulations! You're now ready to capture a profile.

Command-Line Arguments

When launching the XProf server from the command line, you can use the following arguments:

Command Shorthand Default Description
--logdir <path> -l <path> The directory containing XProf profile data (files ending in .xplane.pb). If provided, XProf will load and display profiles from this directory. If omitted, XProf will start without loading any profiles.1
--port <port> -p <port> 8791 The port for the XProf web server.
--grpc_port <port> -g <port> 50051 The port for the gRPC server used for distributed processing. This must be different from --port.
--worker_service_address <addresses> -w <addresses> 0.0.0.0:<grpc_port> A comma-separated list of worker addresses (e.g., host1:50051,host2:50051) for distributed processing.
--hide_capture_profile_button -h N/A If set, hides the 'Capture Profile' button in the UI.
--enable_tab_name_label -e False If set, shows a per-tab name label in the UI.
--src_prefix <prefix> -s <prefix> A prefix prepended to source file paths, used for source-code linking in the UI.
--max_concurrent_worker_requests <n> -m <n> 1 The maximum number of concurrent requests a worker's gRPC server will process, used in distributed profiling.

1 You can dynamically load profiles using session_path or run_path URL parameters, as described in the Log Directory Structure section.

Log Directory Structure

When using XProf, profile data must be placed in a specific directory structure. XProf expects .xplane.pb files to be in the following path:

<log_dir>/plugins/profile/<session_name>/
  • <log_dir>: This is the root directory that you supply to tensorboard --logdir.
  • plugins/profile/: This is a required subdirectory.
  • <session_name>/: Each subdirectory inside plugins/profile/ represents a single profiling session. The name of this directory will appear in the TensorBoard UI dropdown to select the session.

Example:

If your log directory is structured like this:

/path/to/your/log_dir/
└── plugins/
    └── profile/
        ├── my_experiment_run_1/
        │   └── host0.xplane.pb
        └── benchmark_20251107/
            └── host1.xplane.pb

You would launch TensorBoard with:

tensorboard --logdir /path/to/your/log_dir/

The runs my_experiment_run_1 and benchmark_20251107 will be available in the "Sessions" tab of the UI.

You can also dynamically load sessions from a GCS bucket or local filesystem by passing URL parameters when loading XProf in your browser. This method works whether or not you provided a logdir at startup and is useful for viewing profiles from various locations without restarting XProf.

For example, if you start XProf with no log directory:

xprof server

You can load sessions using the following URL parameters.

Assume you have profile data stored on GCS or locally, structured like this:

gs://your-bucket/profile_runs/
├── my_experiment_run_1/
│   ├── host0.xplane.pb
│   └── host1.xplane.pb
└── benchmark_20251107/
    └── host0.xplane.pb

There are two URL parameters you can use:

  • session_path: Use this to load a single session directly. The path should point to a directory containing .xplane.pb files for one session.

    • GCS Example: http://localhost:8791/?session_path=gs://your-bucket/profile_runs/my_experiment_run_1
    • Local Path Example: http://localhost:8791/?session_path=/path/to/profile_runs/my_experiment_run_1
    • Result: XProf will load the my_experiment_run_1 session, and you will see its data in the UI.
  • run_path: Use this to point to a directory that contains multiple session directories.

    • GCS Example: http://localhost:8791/?run_path=gs://your-bucket/profile_runs/
    • Local Path Example: http://localhost:8791/?run_path=/path/to/profile_runs/
    • Result: XProf will list all session directories found under run_path (i.e., my_experiment_run_1 and benchmark_20251107) in the "Sessions" dropdown in the UI, allowing you to switch between them.

Loading Precedence

If multiple sources are provided, XProf uses the following order of precedence to determine which profiles to load:

  1. session_path URL parameter
  2. run_path URL parameter
  3. logdir command-line argument

Distributed Profiling

[!WARNING] Currently, distributed processing only benefits the following tools: overview_page, framework_op_stats, input_pipeline, and pod_viewer.

XProf supports distributed profile processing by using an aggregator that distributes work to multiple XProf workers. This is useful for processing large profiles or handling multiple users.

[!NOTE] The ports used in these examples (6006 for the aggregator HTTP server, 9999 for the worker HTTP server, and 50051 for the worker gRPC server) are suggestions and can be customized.

Worker Node

Each worker node should run XProf with a gRPC port exposed so it can receive processing requests. You should also hide the capture button as workers are not meant to be interacted with directly.

$ xprof server --grpc_port=50051 --port=9999 --hide_capture_profile_button

Aggregator Node

The aggregator node runs XProf with the --worker_service_address flag pointing to all available workers. Users will interact with aggregator node's UI.

$ xprof server --worker_service_address=<worker1_ip>:50051,<worker2_ip>:50051 --port=6006 --logdir=profiler/demo

Replace <worker1_ip>, <worker2_ip> with the addresses of your worker machines. Requests sent to the aggregator on port 6006 will be distributed among the workers for processing.

For deploying a distributed XProf setup in a Kubernetes environment, see Kubernetes Deployment Guide.

Resources

Citing XProf

To cite XProf, please use the following BibTeX entry for the MLSys 2026 paper:

@inproceedings{1076558,
  title     = {XProf: An Open, Scalable and Extensible Profiling System for the Modern ML Stack},
  author    = {Robert Hundt and Naveen Kumar and Jose Baiocchi Paredes and Scott Goodson and Clive Verghese and Prasanna Rengasamy and Kelvin Le and Jiya Zhang and Charles Alaras and Yin Zhang and Kan Cai and Jiten Thakkar and Sai Ganesh Bandiatmakuri and Yogesh SY and Ani Udipi and Vikas Aggarwal},
  year      = {2026},
  booktitle = {Ninth Conference on Machine Learning and Systems}
}

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

xprof_nightly-2.24.1a20260822-py3-none-win_amd64.whl (17.6 MB view details)

Uploaded Python 3Windows x86-64

xprof_nightly-2.24.1a20260822-py3-none-manylinux_2_35_aarch64.whl (32.4 MB view details)

Uploaded Python 3manylinux: glibc 2.35+ ARM64

xprof_nightly-2.24.1a20260822-py3-none-manylinux_2_27_x86_64.whl (18.3 MB view details)

Uploaded Python 3manylinux: glibc 2.27+ x86-64

xprof_nightly-2.24.1a20260822-py3-none-macosx_11_0_arm64.whl (33.3 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

File details

Details for the file xprof_nightly-2.24.1a20260822-py3-none-win_amd64.whl.

File metadata

File hashes

Hashes for xprof_nightly-2.24.1a20260822-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 dc48c1ab8cd9fedb5676894906ea48e3ab3d068956768830e5ec63411a692a73
MD5 41912991b64d2756c5938c927c78cd02
BLAKE2b-256 92f5c95f68e1b6a6391d099d2747828e605af331e02f65c4ff0c07fb8518e2fd

See more details on using hashes here.

File details

Details for the file xprof_nightly-2.24.1a20260822-py3-none-manylinux_2_35_aarch64.whl.

File metadata

File hashes

Hashes for xprof_nightly-2.24.1a20260822-py3-none-manylinux_2_35_aarch64.whl
Algorithm Hash digest
SHA256 de7e5af68fa6ea40e89c3803c2fd5c666a06f3ecea15cb117c2c1ded41473d03
MD5 0a7a0a19a96183d786482a1986cecaae
BLAKE2b-256 2f0812da23483a86a87f946058dd8187413b220cc7d7a104f517e91c3af7b5a8

See more details on using hashes here.

File details

Details for the file xprof_nightly-2.24.1a20260822-py3-none-manylinux_2_27_x86_64.whl.

File metadata

File hashes

Hashes for xprof_nightly-2.24.1a20260822-py3-none-manylinux_2_27_x86_64.whl
Algorithm Hash digest
SHA256 50a9942e996a502e5546035044c1e174718db3537604fb3865c77da65ba99c88
MD5 8064bef8faf55de8caba5b93c21a881d
BLAKE2b-256 e069b85997357f82abbd87f9044cb720b17555f063005a1426f14e1c54c2dd02

See more details on using hashes here.

File details

Details for the file xprof_nightly-2.24.1a20260822-py3-none-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for xprof_nightly-2.24.1a20260822-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 6012aad9c0c13283a1a586f5dc736dc1877ad174aa0ebcb0072d9a215faa1426
MD5 7b1548068b43a34a893fbe173975d177
BLAKE2b-256 009f6147b8630f5284414a6f780df273c19d3bade34b6ede7f02f938e8bfc71f

See more details on using hashes here.

Release history Release notifications | RSS feed

This release

2.24.1a20260822 This release

4 files

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page