EngineProfile

The per-backend tuning the SDF engine reads — construct-scene-evaluator §EV-A10.

In the namespace construct::engine. Declared in src/libs/libconstruct/construct/engine/EngineProfile.hpp.

Detailed description

A process singleton, like rhi::RenderBudget: set once when the device is known, read everywhere afterwards. Read-only after that, so any thread may read it without coordination.

§EV-P11 completes this: profiles as data in `profiles.yaml`, matched on QRhi::Implementation, device type and vendor id, with a `rendering.engine.<key>` settings override per machine, and every value citing the bench row that justifies it. What is here is the subset §EV-P5 consumes, with the generic defaults — which is also what a device with no profile will keep getting once the matching exists.

There is deliberately no environment-variable path into this, for the bench or for anything else. A tuning value that can be set behind the process's back is a value no report can be trusted to describe; the bench sets these through construct-bench's own flags.