PrintTimings

PrintTimings turns on mtmd’s built-in per-step timing output — time spent tokenizing, running the projector, and evaluating chunks. Useful when a vision query is slow and you need to localize the bottleneck.

Quick reference

Type	bool?
Default	null (off)
Category	Multimodal context diagnostics
Field on	MultimodalContextParameters.PrintTimings

What it does

• null or false — no timing output.
• true — mtmd emits per-stage timings through the native logger. Requires EnableDebugLogging or equivalent output routing to see them.

Timings are noisy. Disable in production; keep on only while debugging.

When to change it

Scenario	Value
Default	null
Investigating vision first-token latency	true
Production	null / false

Example

var preset = new Qwen3VL2BPreset();
preset.EngineParameters.EnableDebugLogging = true;
preset.MtmdContextParameters.PrintTimings = true;

using var api = AsposeLLMApi.Create(preset, logger);
// Per-stage mtmd timings now appear in the logs.

Interactions

• EnableDebugLogging — required for timing lines to reach the logger.
• Verbosity — complementary verbosity knob.

What’s next

• Debugging vision — full diagnostic playbook.
• Verbosity — mtmd log-level knob.
• Multimodal context hub — all mtmd knobs.