Skip to content

Add ONNX Runtime GQA-style SDPA benchmark#18716

Open
kimishpatel wants to merge 1 commit into
gh/kimishpatel/236/basefrom
gh/kimishpatel/236/head
Open

Add ONNX Runtime GQA-style SDPA benchmark#18716
kimishpatel wants to merge 1 commit into
gh/kimishpatel/236/basefrom
gh/kimishpatel/236/head

Conversation

@kimishpatel

@kimishpatel kimishpatel commented Apr 6, 2026

Copy link
Copy Markdown
Contributor

Stack from ghstack (oldest at bottom):

Ports the attention algorithm from onnxruntime's gqa_attention_base.h
to enable direct performance comparison against ET's flash attention
and the existing standard SDPA benchmark.

Key differences from standard SDPA: scale baked into GEMM alpha
(saves a scaling pass), scores buffer padded to max_seq_len columns
(matching ONNX's present_buffer_sequence_length), narrow softmax
over valid causal window only (zeros elsewhere, skips exp on masked
positions), and output in [B,S,Hq,D] with stride Hq*D matching
ONNX's interleaved output format.

Validation tests confirm ONNX GQA matches ET custom_sdpa_out within
float32 tolerance.

Authored with Claude.

Differential Revision: D99677677

Ports the attention algorithm from onnxruntime's gqa_attention_base.h
to enable direct performance comparison against ET's flash attention
and the existing standard SDPA benchmark.

Key differences from standard SDPA: scale baked into GEMM alpha
(saves a scaling pass), scores buffer padded to max_seq_len columns
(matching ONNX's present_buffer_sequence_length), narrow softmax
over valid causal window only (zeros elsewhere, skips exp on masked
positions), and output in [B,S,Hq,D] with stride Hq*D matching
ONNX's interleaved output format.

Validation tests confirm ONNX GQA matches ET custom_sdpa_out within
float32 tolerance.

Authored with Claude.

Differential Revision: [D99677677](https://our.internmc.facebook.com/intern/diff/D99677677/)

[ghstack-poisoned]
@pytorch-bot

pytorch-bot Bot commented Apr 6, 2026

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18716

Note: Links to docs will display an error until the docs builds have been completed.

❌ 127 New Failures

As of commit 41e6c73 with merge base fb1618e (image):

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@github-actions

github-actions Bot commented Apr 6, 2026

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 6, 2026
@kimishpatel

Copy link
Copy Markdown
Contributor Author

submitted by accident, not meant to land immedidately

@github-actions

github-actions Bot commented Jun 6, 2026

Copy link
Copy Markdown

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions Bot added the Stale PRs inactive for over 60 days label Jun 6, 2026
@meta-cla

meta-cla Bot commented Jul 3, 2026

Copy link
Copy Markdown

Hi @kimishpatel!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported meta-exported Stale PRs inactive for over 60 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant