NamedFormEvaluation
Published configurations
Existing relative Frobenius budget for the assembled operator oracle.
Measured operation
Measures complete assembly against a frozen full-matrix oracle.
Contexts are scalar mass, diffusion, Helmholtz, vector mass and linear elasticity, with constant or represented field coefficients. First includes form construction, assembly and destruction; Warm retains the form. Ordinary scopes retain mapped geometry. ColdGeometry flushes the mesh's transformation and mapped-quadrature caches before each assembly, outside timing. It includes lazy geometry reconstruction, not merely index-slot allocation, and does not alter topology, spaces or coefficients. These controls must not be interpreted as pure cache allocation latencies. PauseOnly uses identical timer boundaries without changing mesh state, providing a negative control for the measurement protocol. Every final sparse operator is compared with the same precomputed Integral oracle. No solve or error integration is timed. Profilers are opt-in and are not CTest or CI timing gates.
Recorded results
Each case retains its original inputs, iteration policy and correctness checks. Raw reports preserve counters, repetitions and the Google Benchmark context. CPU, wall and manually supplied times are labeled separately; unlike operations and configurations are not averaged together.
Timing history
RodinNamedFormBenchmarks · auto · regular · ranks: 1
No timing history has been published for this component.
Benchmark machine and measurement conditions
Published CI benchmarks run on standard GitHub-hosted ubuntu-24.04
virtual machines for public repositories.
| System | CPU | Memory | SSD |
|---|---|---|---|
| Ubuntu 24.04, x64 | 4 vCPUs | 16 GB | 14 GB |
The benchmark builds use GCC 14 and Release mode. Each job runs one benchmark executable at a time. OpenMP, OpenBLAS and MKL use one thread; MPI ranks share the same runner. The selected configuration identifies the build and rank count.
The CPU model and host load can vary between virtual machines, so small timing differences should be checked across repeated runs. GitHub runner specifications describe the available hardware. The source workflow is BenchmarkGroup.yml.