> For the complete documentation index, see [llms.txt](https://docs.algenta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algenta.ai/benchmarks/overview.md). # Benchmarks How Algenta measures and publishes performance — what each benchmark claims, the baseline it is measured against, and the rules every published number follows. Every result in this section includes its baseline, hardware description, and reproduction command. This section is the index. Each benchmark family has its own page with its own claims, baselines and results, so results can be added without rewriting what is already here. ## Published families


Compute kernels	Dense and quantized matrix kernels, measured against the engine's own prior implementations.	Compute kernels
Least-squares accuracy	Correct digits on the NIST StRD linear-regression suite, against fourteen numpy, scipy and statsmodels arms on the same data.	Least-squares accuracy
Forecasting on the joint axis	Accuracy and latency together on all 100,000 M4 series, against statsforecast 2.1.1 at matched parallelism.	Forecasting on the joint axis
FinQA exact execution	Execution accuracy on all 8,281 real FinQA gold programs, against three real naive-reimplementation arms on the same programs.	FinQA exact execution
LLM tool-calling uplift	gpt-5-mini answering 16 real numeric questions with and without Algenta's tool-calling access to its own compiled engine.	LLM tool-calling uplift
Sort	LSD radix sort over Float64 keys, sequential and parallel, against numpy.sort's introsort across three input orders and six sizes.	Sort
Top-k selection	A SIMD-screened bounded heap against numpy.argpartition — one honest loss at the smallest size and largest k, wins everywhere else.	Top-k selection
Graph betweenness centrality	Brandes betweenness over a CSR adjacency, against networkx — ahead in every cell measured, widening with graph size.	Graph betweenness centrality
Survival analysis	Kaplan-Meier and Cox proportional hazards, against lifelines, on two current real-world datasets — 10 of 11 cells win, from 3.0x to 142.9x.	Survival analysis

More families are added here as they are measured. A family appears above only once it has published numbers and a reproduction command — never as a placeholder. ## The rules every number follows A result appears in this section only if it meets all of the following conditions. {% hint style="info" %} **Measured against the strongest available baseline, not the weakest.** A speedup over an unoptimised reference is an implementation detail. A speedup over the best thing a reader could otherwise use is a result. Each page names its baseline explicitly, and a page whose only baseline is an earlier Algenta implementation says so in its first line rather than presenting the ratio as competitive. {% endhint %} * **The baseline is named and versioned.** "Faster" is meaningless without saying "than what". Where the comparison is against Algenta's own earlier implementation, the page says so plainly rather than implying an external comparison. * **Correctness is asserted alongside every timing.** A faster wrong answer is not a result. Every kernel benchmark diffs its output against a reference implementation and reports the difference. * **Properties are gated, absolute times are not.** Nanoseconds vary by machine, thermal state and load. What must hold is the *shape* — cost per unit of work staying flat as the problem grows, for example. Absolute numbers are printed for tracking and are explicitly not a contract. * **Hardware is reported, never averaged.** Results are published per chip generation and per memory configuration. A single headline number across different hardware hides the only thing a reader needs. * **Measured after warm-up.** First-call costs — page faults on a fresh buffer, a thread pool spinning up — belong to neither implementation. * **Reproducible.** Every page carries the command that produced its table. ## What is not published here * Single-number claims of the form "N times faster", with no shape, no baseline and no hardware. * A self-comparison presented as a competitive one. Where Algenta is measured against its own earlier implementation, the page says so — and where a tuned vendor library is faster, the page says that too rather than omitting the comparison. * A timing taken on a machine that was busy. Benchmarks in this engine check `hot ≤ warm ≤ cold` and a sample-dispersion bound before reporting; a run that fails either is published as invalid with no ratio, because a contended sample and a real regression look identical on the page. * A kernel-level speedup restated as an end-to-end one. A kernel result may be published as a kernel result; it becomes an end-to-end claim only when an end-to-end run demonstrates it. * Results from a configuration a reader cannot reproduce. ## Related * [Compute kernels](/benchmarks/compute-kernels.md) — dense and quantized matrix kernel results. * [NVIDIA kernel benchmarks](/benchmarks/nvidia-kernel-benchmarks.md) — the portable validation kernel measured unmodified on T4, L4 and A100. * [Attention](/benchmarks/attention.md) — tiled attention memory, rotary embedding, and block-size invariance. * [Normalization](/benchmarks/normalization.md) — RMSNorm and LayerNorm, and the price of a safe variance. * [Feed-forward](/benchmarks/feed-forward.md) — gated activations, the two GELU conventions, and embedding cost. * [Forecasting on the joint axis](/benchmarks/forecasting-joint-axis.md) — M4 accuracy and latency measured together against statsforecast 2.1.1. * [LLM tool-calling uplift](/benchmarks/llm-tool-calling-uplift.md) — an LLM answering the same questions with and without access to this engine. * [Runtime libraries](/engine-runtime/runtime-libraries.md) — the surface these kernels are exposed through. * [Runtime library catalog](/engine-runtime/runtime-library-catalog.md) — every module and function the runtime exposes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.algenta.ai/benchmarks/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.