NoPerf
Contents
[
Hide
]
NoPerf disables collection of performance timings inside the native layer. The savings are small but non-zero; useful in very high-throughput production loops.
Quick reference
| Type | bool? |
| Default | null (timings collected) |
| Category | Performance |
| Field on | ContextParameters.NoPerf |
What it does
nullorfalse— timings collected. Minor overhead per call but you can inspect them via native logging.true— timings disabled. Slightly faster; nothing to inspect.
This is a micro-optimization. The savings are usually below measurement noise on a single request. On a high-throughput server processing many requests per second, the savings add up.
When to change it
| Scenario | Value |
|---|---|
| Default (keeps timings for debugging) | null |
| High-throughput production squeezing every last cycle | true |
| Debugging performance | null or false |
Example
var preset = new Qwen25Preset();
preset.ContextParameters.NoPerf = true; // production
preset.EngineParameters.EnableDebugLogging = false;
Interactions
EnableDebugLogging— turning on debug logs defeats the purpose ofNoPerf = true.
What’s next
- Performance issues troubleshooting — throughput-focused tuning.
- Context parameters hub — all context knobs.