Add protocol performance profiles

2026-09-12 11:50:30 +02:00
parent e2a0434941
commit 77be2b39ff
8 changed files with 131 additions and 1 deletions
@@ -95,6 +95,14 @@ PyTorch/ROCm processed the same duration in approximately 98.6 seconds. These
 are validation observations, not performance guarantees or hardware
 requirements. CPU execution remains supported and may be substantially slower.

+Protocol-generation performance is selected through intentionally abstract
+profiles rather than hardware controls in the GUI. `auto` is the default and
+delegates thread selection to the inference backend; with Ollama this means
+omitting `num_thread` entirely. The explicit resource profiles currently map
+`fast` to 16 Ollama CPU threads, `efficient` to 10, and `powersave` to 4. These
+concrete mappings belong to the backend/configuration boundary and may evolve
+independently of the user-facing profile semantics.
+
 ## Meeting Context and Speakers

 `MeetingContext` is a structured domain object containing meeting metadata,