#6386 [GUI] isolate launch configs for concurrent tuning commands

open · @Held0fTheWelt · 0 コメント · GitHub で見る

BenchmarksWindows

本文

## Problem and result

A desktop tune and a concurrent status or expert-settings request can write their launch options to the same model-specific file. The second request can overwrite the options while the tune is still using them. Each command now gets its own launch snapshot, which stays available until that command completes.

## Related discussion

The broader desktop discussion is #6342. This is confined to configuration files used by the native tuning commands.

## Approach

Write each command's input to a uniquely named file under the native tuning directory. Omit the live instance key and port as before. Use the same snapshot lifecycle for status, effective settings, turning tuning off, undo, tune, and recheck. Remove each snapshot when its command completes.

## Validation

**Passed:**
- Windows, Node v24.15.0, commit `39ce969d2`. `node --test app/host/tests/native-autotune.test.mjs` passed all 9 tests. The overlapping-request case checks that the ongoing tune retains its original bytes and both commands clean up their files.
- `git diff --check upstream/main...HEAD` returned 0.

**Failed:**
- None observed in the checks above.

**Not run:**
- Full desktop build and live GPU tuning. The test uses a fake launcher to control request overlap.

## Limits

This change affects how native tuning commands receive configuration. It does not change the benchmark algorithm or introduce new tuning defaults.

関連リンク

インストール・モデル・リリースへのサイト内リンク。