live wire
▸Snowflake agent evals can pin judge versions; unpinned metrics may roll forward and shift scoresSnowflake▸ThoughtSpot makes Spotter 3 default for new instances; it requires download rights and always shares query data with an LLMThoughtSpot documentation▸MotherDuck adds image classification and object location to prompt_jev(), returning typed SQL outputs with confidence scoresMotherDuck▸BigQuery conversational analytics adds Montréal and Toronto; mixed-region agents still default to globalGoogle Cloud Documentation▸Fabric enables Azure OpenAI Copilot access by default, but OpenAI-subprocessor and cross-region processing/storage switches remain offMicrosoft Learn▸Snowflake Cortex Agents now continue by default when named tools are inaccessible, emitting warnings instead of failing the runSnowflake documentation▸Databricks Genie One can use group memberships to tailor answers, while Unity Catalog remains the access-control boundaryDatabricks documentation▸Fabric data agents can query Power BI models with Read alone; Build and workspace access are unnecessaryMicrosoft Learn▸Fabric data-agent Git configs expose column flags, but selecting a table still includes every columnMicrosoft Learn▸Google Data Agent Kit offers remote Spark kernels, but notebook exports can still move results into local Pandas or ArrowGoogle Cloud Documentation▸Cube says production analytics agents need explicit partial-result states, caller-filtered model search and durable artifactsCube▸Thinking Machines names Bridgewater behind ReViSQL-K2.6, citing 92.97% SC-16 accuracy at 15% of frontier-model costThinking Machines Lab▸AWS says a mismatched data/tool/prompt release cut its Field Sales agent pass rate from 78% to 38% in pre-productionAWS Artificial Intelligence Blog▸NL2SQL Multi-Agent ships evaluation artifacts across BIRD, CSpider, Archer and KDD DataSpace—but no software licenseGitHub▸Snowflake agent evals can pin judge versions; unpinned metrics may roll forward and shift scoresSnowflake▸ThoughtSpot makes Spotter 3 default for new instances; it requires download rights and always shares query data with an LLMThoughtSpot documentation▸MotherDuck adds image classification and object location to prompt_jev(), returning typed SQL outputs with confidence scoresMotherDuck▸BigQuery conversational analytics adds Montréal and Toronto; mixed-region agents still default to globalGoogle Cloud Documentation▸Fabric enables Azure OpenAI Copilot access by default, but OpenAI-subprocessor and cross-region processing/storage switches remain offMicrosoft Learn▸Snowflake Cortex Agents now continue by default when named tools are inaccessible, emitting warnings instead of failing the runSnowflake documentation▸Databricks Genie One can use group memberships to tailor answers, while Unity Catalog remains the access-control boundaryDatabricks documentation▸Fabric data agents can query Power BI models with Read alone; Build and workspace access are unnecessaryMicrosoft Learn▸Fabric data-agent Git configs expose column flags, but selecting a table still includes every columnMicrosoft Learn▸Google Data Agent Kit offers remote Spark kernels, but notebook exports can still move results into local Pandas or ArrowGoogle Cloud Documentation▸Cube says production analytics agents need explicit partial-result states, caller-filtered model search and durable artifactsCube▸Thinking Machines names Bridgewater behind ReViSQL-K2.6, citing 92.97% SC-16 accuracy at 15% of frontier-model costThinking Machines Lab▸AWS says a mismatched data/tool/prompt release cut its Field Sales agent pass rate from 78% to 38% in pre-productionAWS Artificial Intelligence Blog▸NL2SQL Multi-Agent ships evaluation artifacts across BIRD, CSpider, Archer and KDD DataSpace—but no software licenseGitHub
nl2sql.ai
benchmarkBENCHMARK

The fastest attention backend for tabular models depends on which axis it reads

SAP’s runnable A100/H100/B200 benchmark finds more than a 3× gap between backends—and no single kernel wins across row and column attention.

By The Benchmark Desk· Sep 28, 2026the quick take — two AI hosts go live when you do

A new runnable benchmark from SAP shows that attention-kernel choice for tabular foundation models cannot be reduced to “use the newest FlashAttention.” The winning backend changes with the table axis, sequence length and GPU generation—and the gap between the best and worst backend can exceed 3× for the same tensor shape.

The September 25 study evaluates five training-capable backends—PyTorch SDPA efficient, SDPA cuDNN, FlashAttention 2, 3 and 4—plus the inference-only vLLM and SageAttention implementations. Its main configuration uses 12 heads, a head dimension of 64 and bfloat16 across NVIDIA A100, H100 and B200 GPUs. Column tests hold rows at 1,024 and sweep 16–2,048 columns; row tests hold columns at 64 and sweep 32–131,072 rows.

The table axis changes the answer

Column attention operates over the contiguous dimension of the benchmark’s row-first tensor layout. Here, cuDNN is a strong cross-platform default: it leads H100 column throughput between 128 and 1,000 columns, while FlashAttention 3 edges ahead only at longer sequences. On B200, FlashAttention 4 leads through 256 columns, but cuDNN overtakes it at longer column sequences.

Row attention reverses that pattern because PyTorch’s SDPA path must make contiguous copies of query, key and value. On A100 and H100, FlashAttention 3 leads except below 128 rows, reaching up to 3.5× the SDPA-efficient baseline and about 1.5× cuDNN. On B200, FlashAttention 4 leads most of the tested range, but cuDNN retakes the lead beyond 8,000 rows.

Hardware alone therefore does not determine the kernel. The paper reports that B200’s best backends exceed the best H100 column-attention throughput by more than 2× and A100 by more than 5×, yet even B200 changes winners as sequence length grows.

A benchmark teams can actually rerun

This result clears a bar many systems papers do not: SAP published the benchmark runner, tests, backend-specific dependency groups, plotting scripts and raw-result workflow. The repository includes make targets for A100/H100/B200 runs, stores results by GPU, dtype and backend, and flushes each completed shape to JSON. That makes the crossover claims inspectable rather than merely plotted in a paper.

The practical H100 recommendation for the paper’s main shape is deliberately mixed: use cuDNN for column attention and FlashAttention 3 for row attention, with SDPA efficient as a possible fallback for very short sequences. For inference beyond 16,000 rows, SageAttention can lead row throughput, but it is approximate and quantized; predictive quality must be checked separately.

The limit is equally important. This is an isolated-kernel benchmark on synthetic tensors, not an end-to-end TabPFN or TabICL training run. It ignores surrounding layers, data movement and the train/query cross-attention details of specific model families. The benchmark establishes that backend selection materially changes kernel throughput. It does not yet establish the same multiplier for full-model latency or model quality.

Filed by The Benchmark Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.