Benchmark Dispatch #460
github-actions[bot]benchmark_dispatch.yml
on: workflow_dispatch
gen-matrix-b200
/
gen
4s
gen-matrix-h100
/
gen
2s
gen-matrix-mi325x
/
gen
2s
Matrix: run-b200
Matrix: run-h100
Matrix: run-mi325x
Annotations
82 errors and 22 warnings
|
run-b200 (rms_norm) / benchmark-cu130-rms_norm-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (rms_norm) / benchmark-cu130-rms_norm-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (grouped_gemm) / benchmark-cu130-grouped_gemm-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (grouped_gemm) / benchmark-cu130-grouped_gemm-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (kl_div) / benchmark-cu130-kl_div-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (kl_div) / benchmark-cu130-kl_div-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (jsd) / benchmark-cu130-jsd-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (jsd) / benchmark-cu130-jsd-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (int4_gemm) / benchmark-cu130-int4_gemm-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (int4_gemm) / benchmark-cu130-int4_gemm-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (cross_entropy) / benchmark-cu130-cross_entropy-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (cross_entropy) / benchmark-cu130-cross_entropy-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (layer_norm-bwd) / benchmark-cu130-layer_norm-bwd-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (layer_norm-bwd) / benchmark-cu130-layer_norm-bwd-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (softmax) / benchmark-cu130-softmax-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (softmax) / benchmark-cu130-softmax-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (rms_norm-bwd) / benchmark-cu130-rms_norm-bwd-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (rms_norm-bwd) / benchmark-cu130-rms_norm-bwd-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (layer_norm) / benchmark-cu130-layer_norm-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (layer_norm) / benchmark-cu130-layer_norm-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (flash_attention) / benchmark-cu130-flash_attention-py3.12-b200
Process completed with exit code 1.
|
|
run-b200 (flash_attention) / benchmark-cu130-flash_attention-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (flash_attention) / benchmark-cu130-flash_attention-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (flash_attention) / benchmark-cu128-flash_attention-py3.12-h100
Process completed with exit code 1.
|
|
run-h100 (flash_attention) / benchmark-cu128-flash_attention-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (flash_attention) / benchmark-cu128-flash_attention-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (grouped_gemm) / benchmark-cu128-grouped_gemm-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (grouped_gemm) / benchmark-cu128-grouped_gemm-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-mi325x (jsd,rms_norm) / benchmark-rocm7.1-jsd,rms_norm-py3.12-mi325x
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-mi325x (jsd,rms_norm) / benchmark-rocm7.1-jsd,rms_norm-py3.12-mi325x
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (welford) / benchmark-cu130-welford-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (welford) / benchmark-cu130-welford-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (kl_div) / benchmark-cu128-kl_div-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (kl_div) / benchmark-cu128-kl_div-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (cross_entropy) / benchmark-cu128-cross_entropy-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (cross_entropy) / benchmark-cu128-cross_entropy-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (rms_norm) / benchmark-cu128-rms_norm-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (rms_norm) / benchmark-cu128-rms_norm-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (gemm) / benchmark-cu128-gemm-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (gemm) / benchmark-cu128-gemm-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (jsd) / benchmark-cu128-jsd-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (jsd) / benchmark-cu128-jsd-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (rms_norm-bwd) / benchmark-cu128-rms_norm-bwd-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (rms_norm-bwd) / benchmark-cu128-rms_norm-bwd-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-mi325x (kl_div,cross_entropy) / benchmark-rocm7.1-kl_div,cross_entropy-py3.12-mi325x
The job has exceeded the maximum execution time of 6h0m0s
|
|
run-mi325x (kl_div,cross_entropy) / benchmark-rocm7.1-kl_div,cross_entropy-py3.12-mi325x
The operation was canceled.
|
|
run-mi325x (kl_div,cross_entropy) / benchmark-rocm7.1-kl_div,cross_entropy-py3.12-mi325x
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-mi325x (kl_div,cross_entropy) / benchmark-rocm7.1-kl_div,cross_entropy-py3.12-mi325x
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-mi325x (int4_gemm,flash_attention) / benchmark-rocm7.1-int4_gemm,flash_attention-py3.12-mi325x
The job has exceeded the maximum execution time of 6h0m0s
|
|
run-mi325x (int4_gemm,flash_attention) / benchmark-rocm7.1-int4_gemm,flash_attention-py3.12-mi325x
The operation was canceled.
|
|
run-mi325x (int4_gemm,flash_attention) / benchmark-rocm7.1-int4_gemm,flash_attention-py3.12-mi325x
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-mi325x (int4_gemm,flash_attention) / benchmark-rocm7.1-int4_gemm,flash_attention-py3.12-mi325x
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-mi325x (softmax,layer_norm-bwd,grouped_gemm) / benchmark-rocm7.1-softmax,layer_norm-bwd,grouped_gemm-py3.12-mi325x
The job has exceeded the maximum execution time of 6h0m0s
|
|
|
|
run-mi325x (softmax,layer_norm-bwd,grouped_gemm) / benchmark-rocm7.1-softmax,layer_norm-bwd,grouped_gemm-py3.12-mi325x
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-mi325x (softmax,layer_norm-bwd,grouped_gemm) / benchmark-rocm7.1-softmax,layer_norm-bwd,grouped_gemm-py3.12-mi325x
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-mi325x (layer_norm,gemm) / benchmark-rocm7.1-layer_norm,gemm-py3.12-mi325x
The job has exceeded the maximum execution time of 6h0m0s
|
|
run-mi325x (layer_norm,gemm) / benchmark-rocm7.1-layer_norm,gemm-py3.12-mi325x
The operation was canceled.
|
|
run-mi325x (layer_norm,gemm) / benchmark-rocm7.1-layer_norm,gemm-py3.12-mi325x
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-mi325x (layer_norm,gemm) / benchmark-rocm7.1-layer_norm,gemm-py3.12-mi325x
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-mi325x (welford,rms_norm-bwd) / benchmark-rocm7.1-welford,rms_norm-bwd-py3.12-mi325x
The job has exceeded the maximum execution time of 6h0m0s
|
|
run-mi325x (welford,rms_norm-bwd) / benchmark-rocm7.1-welford,rms_norm-bwd-py3.12-mi325x
The operation was canceled.
|
|
run-mi325x (welford,rms_norm-bwd) / benchmark-rocm7.1-welford,rms_norm-bwd-py3.12-mi325x
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-mi325x (welford,rms_norm-bwd) / benchmark-rocm7.1-welford,rms_norm-bwd-py3.12-mi325x
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (welford) / benchmark-cu128-welford-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (welford) / benchmark-cu128-welford-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (gemm) / benchmark-cu130-gemm-py3.12-b200
The job has exceeded the maximum execution time of 6h0m0s
|
|
run-b200 (gemm) / benchmark-cu130-gemm-py3.12-b200
The operation was canceled.
|
|
run-b200 (gemm) / benchmark-cu130-gemm-py3.12-b200
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-b200 (gemm) / benchmark-cu130-gemm-py3.12-b200
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (layer_norm) / benchmark-cu128-layer_norm-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (layer_norm) / benchmark-cu128-layer_norm-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (int4_gemm) / benchmark-cu128-int4_gemm-py3.12-h100
The job has exceeded the maximum execution time of 6h0m0s
|
|
run-h100 (int4_gemm) / benchmark-cu128-int4_gemm-py3.12-h100
The operation was canceled.
|
|
run-h100 (int4_gemm) / benchmark-cu128-int4_gemm-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (int4_gemm) / benchmark-cu128-int4_gemm-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (softmax) / benchmark-cu128-softmax-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (softmax) / benchmark-cu128-softmax-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-h100 (layer_norm-bwd) / benchmark-cu128-layer_norm-bwd-py3.12-h100
The job has exceeded the maximum execution time of 6h0m0s
|
|
run-h100 (layer_norm-bwd) / benchmark-cu128-layer_norm-bwd-py3.12-h100
The operation was canceled.
|
|
run-h100 (layer_norm-bwd) / benchmark-cu128-layer_norm-bwd-py3.12-h100
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
|
|
run-h100 (layer_norm-bwd) / benchmark-cu128-layer_norm-bwd-py3.12-h100
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
|
|
run-b200 (rms_norm) / upload-benchmark-results / Uploading benchmark-results-b200-rms_norm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (grouped_gemm) / upload-benchmark-results / Uploading benchmark-results-b200-grouped_gemm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (kl_div) / upload-benchmark-results / Uploading benchmark-results-b200-kl_div
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (jsd) / upload-benchmark-results / Uploading benchmark-results-b200-jsd
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (int4_gemm) / upload-benchmark-results / Uploading benchmark-results-b200-int4_gemm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (cross_entropy) / upload-benchmark-results / Uploading benchmark-results-b200-cross_entropy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (layer_norm-bwd) / upload-benchmark-results / Uploading benchmark-results-b200-layer_norm-bwd
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (softmax) / upload-benchmark-results / Uploading benchmark-results-b200-softmax
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (rms_norm-bwd) / upload-benchmark-results / Uploading benchmark-results-b200-rms_norm-bwd
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (layer_norm) / upload-benchmark-results / Uploading benchmark-results-b200-layer_norm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (grouped_gemm) / upload-benchmark-results / Uploading benchmark-results-h100-grouped_gemm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-mi325x (jsd,rms_norm) / upload-benchmark-results / Uploading benchmark-results-mi325x-jsd,rms_norm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-b200 (welford) / upload-benchmark-results / Uploading benchmark-results-b200-welford
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (kl_div) / upload-benchmark-results / Uploading benchmark-results-h100-kl_div
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (cross_entropy) / upload-benchmark-results / Uploading benchmark-results-h100-cross_entropy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (rms_norm) / upload-benchmark-results / Uploading benchmark-results-h100-rms_norm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (gemm) / upload-benchmark-results / Uploading benchmark-results-h100-gemm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (jsd) / upload-benchmark-results / Uploading benchmark-results-h100-jsd
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (rms_norm-bwd) / upload-benchmark-results / Uploading benchmark-results-h100-rms_norm-bwd
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (welford) / upload-benchmark-results / Uploading benchmark-results-h100-welford
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (layer_norm) / upload-benchmark-results / Uploading benchmark-results-h100-layer_norm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-h100 (softmax) / upload-benchmark-results / Uploading benchmark-results-h100-softmax
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@65a9edc5881444af0b9093a5e628f2fe47ea3b2e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
benchmark-results-b200-cross_entropy
|
634 Bytes |
sha256:59e41be4d71c6d0f3eb800b4a9ab478b39147f6c79c5c18cf6ef20af95e31555
|
|
|
benchmark-results-b200-grouped_gemm
|
150 Bytes |
sha256:43f1d3b408d95b6d0c2ae62c1363e31be4d2a11829097a712fd1d4b2c416f861
|
|
|
benchmark-results-b200-int4_gemm
|
602 Bytes |
sha256:c922b8c2970fa6f199f7d16246cc977564ab7db2d596ee25abd920ddd71f092e
|
|
|
benchmark-results-b200-jsd
|
609 Bytes |
sha256:a803e74e2a6dfa85310d92c68b3375f822c565376aa154afb311c8afba804679
|
|
|
benchmark-results-b200-kl_div
|
506 Bytes |
sha256:452c9d364bac4ddfc7f08c47bca5e90d9bdf9540ea3239aa9c50e0ea885a2f38
|
|
|
benchmark-results-b200-layer_norm
|
1.06 KB |
sha256:910ddb183fc94e4d4ee3ed42fdecfd61c6fae710e5574935441e77ebca91d36e
|
|
|
benchmark-results-b200-layer_norm-bwd
|
756 Bytes |
sha256:a8dfb9a7330b6c6fb4392dd3f88a2a809587eaf66b721a730b382d2429258657
|
|
|
benchmark-results-b200-rms_norm
|
618 Bytes |
sha256:317cbf45360237a9915fb69486390e0650dc6c2c954113b97fcebfd2a7131d99
|
|
|
benchmark-results-b200-rms_norm-bwd
|
591 Bytes |
sha256:a81e20db2ef1dd9054f17f890a0ecafca928a971171eb80aa34db66cd2472837
|
|
|
benchmark-results-b200-softmax
|
1.05 KB |
sha256:81d748b9a9eea9ab95b494aef9dd4d601781079564ebd0db2257ef4bedae9fdb
|
|
|
benchmark-results-b200-welford
|
602 Bytes |
sha256:ef640c9eb6da50a8ac47dd8c55568a01cb75f1d5722c70c08f278842b5b1b8ff
|
|
|
benchmark-results-h100-cross_entropy
|
631 Bytes |
sha256:fca595ca2d20884d020dc04d7e10b5d95a26d43b8a261cf290b71c751a569e71
|
|
|
benchmark-results-h100-gemm
|
683 Bytes |
sha256:e90097a41c8f75bbd296fd9fac482bd10bfdae4fab9f279a763dbf3abd1c45fc
|
|
|
benchmark-results-h100-grouped_gemm
|
539 Bytes |
sha256:e3a47c2097498fda42a03425e51e6f68515d6079f904001e9543f24a2686e114
|
|
|
benchmark-results-h100-jsd
|
614 Bytes |
sha256:01ff2b8d81d9ee75270c2b253cf4d859e459751bc85856f46951f595147debd8
|
|
|
benchmark-results-h100-kl_div
|
614 Bytes |
sha256:8b4d63c39a2f4083263a8b25dc69031ab72d25fba13f7a945443692c73e4ab8d
|
|
|
benchmark-results-h100-layer_norm
|
1.04 KB |
sha256:27b6384f51edb90c665034883770469c6e237234c3b5ff7ce1b6cd01d0945b4a
|
|
|
benchmark-results-h100-rms_norm
|
616 Bytes |
sha256:f9d9a4d39b91885b2cca040458e42f150ed97590a8fb2ca58f97033c347d0183
|
|
|
benchmark-results-h100-rms_norm-bwd
|
589 Bytes |
sha256:9764dbbeebe65483c186b53200df42a91844d4192d613e5f38a2efce47ecb501
|
|
|
benchmark-results-h100-softmax
|
1.05 KB |
sha256:d3103405eec07538dc842ab9dba84bd9ec3b287090f0b840844e1bda0d8e1708
|
|
|
benchmark-results-h100-welford
|
603 Bytes |
sha256:6deb387aa0956e4a268bbacf8e1c439f360e122c447bdf754f2e43c41b185b14
|
|
|
benchmark-results-mi325x-jsd,rms_norm
|
901 Bytes |
sha256:2c407d0a19aef4e8d3e40063df28db402e65d3d3169ad7b4a61420b752fbc540
|
|