Skip to content

prefill: --prefill-help and --prefill-help-frac as the official flags for the idle-stage helper - #1247

Closed
anon761 wants to merge 1 commit into
Niko1221:mainfrom
anon761:prefill-help-flag
Closed

anon761 wants to merge 1 commit into
Niko1221:mainfrom
anon761:prefill-help-flag

Conversation

@anon761

@anon761 anon761 commented Oct 6, 2026

Copy link
Copy Markdown

STRATA_PREFILL_HELP / STRATA_PREFILL_HELP_FRAC already do the work, but env-only is awkward when every other knob has a flag. These two set them before Prefill reads them, so the behavior is identical and repeatable; the envs stay honoured for existing configs.\n\nMeasured on a two-card layer split (2x RTX 3090): about +30% prompt-read time on small prompts (~1.4K tokens), where the second card otherwise sits idle during the first chunk.

… for the idle-stage helper (the envs stay honoured)
@anon761
anon761 force-pushed the prefill-help-flag branch from 6f0c186 to fea3bf4 Compare October 6, 2026 20:01
fragtion pushed a commit to fragtion/StrataPool that referenced this pull request Oct 7, 2026
…-help-frac as the official flags for the idle-stage helper (the envs stay honoured)

prefill: --prefill-help and --prefill-help-frac as the official flags for the idle-stage helper (the envs stay honoured)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0157fjixQD2nRxvCvtXq66DD
@Niko1221

Copy link
Copy Markdown
Owner

Thanks. The idle-stage helper is already in as STRATA_PREFILL_HELP / STRATA_PREFILL_HELP_FRAC; the PR only adds flags for them, so it is outside the speed round. We would take the flags in a small rebased PR.

@Niko1221

Copy link
Copy Markdown
Owner

Thanks for the pull request.

We're resetting the tracker for 0.2.0-beta. There are more than 1,300 open issues and pull requests, too many for us to review properly, so we're closing everything that isn't being worked on right now. Closed here does not mean rejected.

To reopen it takes about two minutes:

  1. Rebase on main if it no longer applies, and re-run your checks on 0.2.0-beta.
  2. Start the title with its area: [Engine], [GUI], [TUI], [Benchmark], [Docs] or [Other].
  3. Fill in the pull request template: the problem and result, and the validation (what you ran, on which revision, what you saw).
  4. Comment /reopen. A check runs and either reopens the pull request or lists what is still missing.

The rules are in CONTRIBUTING.md.

@Niko1221 Niko1221 closed this Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants