- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces PersonTTS, a framework for personalized test-time scaling that aims to satisfy user-specific accuracy, latency, and inference-cost requirements jointly. The proposed approach employs an LLM agent to discover executable TTS controllers and amortizes the discovery process through requirement-matched policy initialization and procedural guidance distilled from historical search experience. Experiments on AIME and HMMT using six Qwen3 models demonstrate substantial improvements in joint satisfaction rate over the evaluated TTS baselines, with additional benefits from cross-user experience reuse.
Critical strengths
S1. Interesting and practically relevant research problem. The paper highlights an important limitation of existing TTS approaches that primarily optimize accuracy against individual resource dimensions. Considering accuracy, latency, and inference cost jointly is meaningful for deploying LLM reasoning services under heterogeneous user requirements.
S2. Promising empirical results and systematic evaluation. PersonTTS achieves substantial improvements in JSR over the evaluated baselines. The paper also includes ablations of the experience-reuse mechanisms, held-out problem evaluation, and experience-bank scaling analysis, providing useful evidence about the proposed framework.
Critical weaknesses
W1. Limited methodological novelty. The framework largely extends AutoTTS by adopting a joint requirement satisfaction objective and standard experience-reuse techniques. Its main mechanisms, nearest-neighbor policy retrieval and LLM-based procedural guidance, are relatively straightforward, offering limited methodological advancement.
W2. Insufficient methodological insights and design principles. The paper lacks principled justification for its design choices, particularly why requirement similarity implies controller transferability and what generalizable insights emerge from historical searches. The theoretical analysis is also weakly connected to the actual retrieval and policy-revision mechanisms.
W3. Insufficiently fair baseline comparisons. PersonTTS directly optimizes JSR, while AutoTTS optimizes accuracy–cost trade-offs and other baselines use predefined strategies. The large improvements may therefore primarily reflect objective alignment. Comparisons with JSR-optimized AutoTTS and simpler constraint-aware searches under matched budgets are needed.
W4. Restricted TTS search space without verifiers. The controller space excludes verifier-guided strategies using outcome or process reward models, which can improve candidate selection and compute allocation. This restriction, along with the absence of verification-guided baselines, limits the generality of the reported results.
W5. Limited evaluation across LLM families. All six evaluated models belong to the Qwen3 family. Without experiments on other model families, it remains unclear whether the discovered controllers and reusable experience generalize across different reasoning behaviors and efficiency characteristics.
W6. Limited benchmark diversity. Evaluation is restricted to AIME and HMMT, two closely related mathematical reasoning benchmarks, with only 30 held-out problems each. The lack of broader tasks, such as scientific reasoning and coding, limits evidence for cross-domain generalization.
W7. Insufficient analysis of experience transfer and negative transfer. Cross-user reuse yields inconsistent benefits. On HMMT25, removing warm-start improves JSR from 77.28% to 79.09%, while increasing the experience-bank size from 20 to 100 reduces JSR from 86.09% to 77.28% (Tables 1 and 3). These findings raise questions about retrieval reliability and the conditions under which historical experience helps or harms generalization.
Questions for authors
Q1. How much of the improvement comes from optimizing JSR rather than from the proposed discovery framework? Could the authors compare against AutoTTS directly optimizing JSR and simpler constraint-aware controller searches under matched action spaces and discovery budgets?
Q2. Why are explicit verifier mechanisms excluded from the controller space? Could the authors provide evidence of PersonTTS's effectiveness with verifier-guided TTS baselines and across additional LLM families or reasoning domains?
Q3. What empirical principles justify requirement-similarity retrieval and procedural guidance, and when does historical experience produce negative transfer? In particular, why does increasing the experience-bank size substantially reduce HMMT held-out performance (Table 3), and how does the total amortized cost change when source-policy discovery and Guide construction are included?
9 comments
Response to Reviewer gY8h - Part II
W2 and Q3: Design principles for initialization and procedural guidance
Thank you for drawing attention to how requirement similarity relates to controller transferability. Your question prompted us to refine the warm-start selection criterion. Originally, we ranked historical users by the Euclidean distance between their requirement profiles and the Target's, using profile similarity as an indirect proxy for controller usefulness. The initialization objective is to choose the historical controller with the highest JSR under the Target requirements on Target-Discovery questions (revised Section 3.3, Equation (5)). We therefore evaluate all 100 Source controllers with 100 Replay seeds, entirely on CPU using the cached Replay pool (Appendix B.2), and select the highest Discovery JSR, choosing randomly among tied maximizers. In Full, the selected historical controller then enters Guide-assisted discovery, which uses the same selection rule.
Retrieval-only executes the selected historical program before any Agent proposal, isolating the effect of this selection refinement. Target-based selection improves Held-out joint satisfaction on both benchmarks, with the larger improvement on HMMT (revised Appendix D.3, Table 8). The weaker HMMT distance-selected initializers reflect choosing through requirement similarity; evaluating actual Target-Discovery performance identifies historical programs that transfer better to the new user's questions. The warm-start-only ablation then retains subsequent discovery from the selected controller but removes the Guide, allowing us to examine procedural guidance separately from choosing the starting program.
The Guide complements initialization by distilling Source code changes, constraint diagnostics, and outcomes into conditional revision rules (revised Section 3.3 and Appendices H–I). The rule depends on the diagnosed failure and available resources: an accuracy shortfall with unfinished reasoning can motivate additional depth when resources permit, whereas a latency violation can motivate a shorter schedule. The following archived AIME24–25 Source cases illustrate how these different diagnoses lead to different revisions.
| Source profile | Failing constraint | Observed depth schedule | Discovery JSR |
|---|---|---|---|
| 0017 | Accuracy | [3] [3,12] | 0% 100% |
| 0039 | Latency | [25] [15] | 0% 100% |
Guide-only achieves higher mean Held-out JSR than independent discovery on both benchmarks, showing that Source-derived revision rules can help new users independently of historical-controller initialization. Together with retrieval-only, this comparison separates two useful roles of experience: selecting a suitable initial program and diagnosing how to revise a program under the new requirements (revised Section 4.3 and Appendix D.3).
Revision. Section 3.4 and Appendix E explain how requirement changes affect thresholds and execution, while Section 4.3 reports the reuse ablations.
Response to Reviewer gY8h - Part III
W7 and Q3: Transfer effects, bank scaling, and amortized cost
Thank you for asking when reuse can become harmful. For HMMT Target profile 0000, Full's additional selective continuation improves accuracy-constraint satisfaction but introduces cost violations, reducing Held-out joint satisfaction even though latency remains satisfied (revised Appendix D.3). The failure condition is limited compute headroom: a revision that resolves the accuracy bottleneck can consume the margin needed to satisfy another constraint. The aggregate ablations also show different component contributions. Full has higher mean JSR than Guide-only on both benchmarks, while warm-start-only leads Full slightly on HMMT. The paired intervals leave the average incremental benefit of each component uncertain, consistent with these benchmark-dependent rankings (Table 9).
An archived grading audit explains the original large bank-size reversal: correcting false-negative HMMT answer grades removes the large disadvantage of the original 100-entry bank while preserving the controllers, profiles, bank membership, and resource records. These historical runs retain distance-based initialization. The completed bank-scaling experiment in the revised manuscript separately samples nested 20-entry and 60-entry banks with five bank-sampling seeds, keeping the Guide and candidate-evaluation budget fixed (Section 4.4.2). Larger banks improve Discovery JSR on both benchmarks and Held-out JSR on AIME; HMMT has an intermediate dip and reaches its highest Held-out value with the full bank (Table 3). This pattern supports broader coverage of useful starting programs as the benefit of bank growth, with generalization depending on which controllers that coverage makes available.
We examine discovery variability through three independent Full runs on the same 20 AIME Targets. Their closely grouped run means and positive paired comparison with the fixed R0 independent-discovery reference support a consistent reuse benefit across these repeated Full searches (revised Appendix D.5).
Full's higher joint satisfaction comes with additional adaptation expenditure (revised Table 2 and Appendix D.4). Our utility analysis therefore values successful service and charges unsuccessful service as a loss: a successful batch earns a net reward equal to independent discovery's average batch inference cost, while a failed batch incurs its inference expenditure. The calculation uses 30 service batches of 30 questions per Target under unchanged requirements, reuses the selected controllers, and charges Full's additional adaptation expenditure (Appendix D.4, Equation (11)). The preparation scenarios identify the main economic distinction. Building a Source bank specifically for future reuse requires many subsequent Targets to recover the investment; when Source searches have already served historical users, only the incremental Guide preparation remains to recover, substantially shortening that period (Table 10). Reusing service histories therefore makes the value of higher satisfaction available sooner to offset preparation.
Revision. Appendix D.3 includes the profile 0000 negative-transfer case and paired transfer analysis, and Section 4.4.2 reports the completed bank-scaling experiment.
W4 and Q2: Alignment with established TTS strategies
Thank you for suggesting verifier-guided strategies. Following the main experimental settings of AutoTTS [1] and Parallel-Probe [2], we use task-model probe answers, cross-branch agreement, and reasoning progress to guide continuation, pruning, stopping, and voting. Together with model selection and self-refinement, these primitives support personalized allocation (revised Section 3.1, Equation (1), and Appendix G). Probe-generation time and tokens are included in resource accounting (revised Appendix B.2).
Revision. Section 3.1, Eq. (1), and Appendices C and G specify the controller interface, while Appendix B.2 includes probe-generation time and tokens in resource accounting.
Response to Reviewer gY8h - Part I
Dear Reviewer gY8h, thank you for your assessment of the contribution and suggestions on comparisons and transfer. Your comments helped us improve the initialization mechanism and the evidence for experience reuse.
W1, W3, and Q1: Problem contribution and objective-matched comparisons
Thank you for your assessment. Our primary contribution is the formulation of Personalized Test-Time Scaling: discovering controllers that jointly satisfy each user's accuracy, latency, and inference-cost requirements. Different requirements favor different controllers, motivating the reuse of prior searches as new users arrive. Building on AutoTTS, PersonTTS provides a simple and effective strategy that combines historical-controller initialization with a Guide distilled from previous searches (revised Sections 1–2 and 3.3).
To assess this contribution under a common objective, the revised baselines include ASC, ESC, ParallelProbe, and our profile-conditioned, JSR-optimized AutoTTS implementation, reported as PersonTTS without reuse and referred to below as independent discovery (revised Section 4.2 and Table 1). ASC, ESC, and ParallelProbe select configurations, while AutoTTS discovers controllers using Full's action API, evaluator, feedback, and five scored proposals without historical initialization or the Guide. All methods optimize Discovery JSR and freeze their selected strategies before Held-out evaluation. Full adds experience reuse by screening 100 Source controllers with 100 Target-Discovery Replay seeds and using the Guide during subsequent discovery. Candidate and final evaluations use 1,000 seeds. The common five-proposal budget therefore refers to scored discovery proposals; historical-controller screening is additional evaluation work reported separately (revised Appendices B.4 and D.4).
Random Search and Bayesian Optimization provide complementary controls for configuration search over the 1,260-point grid, with 100 Source and 20 Target profiles per benchmark. Each selects the highest Discovery-JSR configuration found within a time cap based on historical Source discovery. Appendix D.2 describes this historical-time budget and the evaluation protocol. The table combines their results in revised Table 7 with controller-discovery results in revised Table 1, reporting mean JSR (%) across both profile and question splits.
The independent-discovery control improves over the evaluated configuration searches, indicating the value of adapting continuation, pruning, voting, and stopping logic to the user's joint requirements. Full then improves over that same discovery framework, locating an additional benefit in cross-user experience reuse (revised Table 1 and Appendix D.2). The two comparisons therefore address different questions: whether a richer controller can better meet personalized constraints, and whether historical experience helps discover it. The stronger ASC control that also tunes self-refinement remains below Full on both benchmarks, so the advantage persists when configuration selection can adjust refinement effort as well.
Revision. Sections 1–2 clarify the personalized joint-constraint problem and contribution, while Section 3.3 describes how initialization and the Guide support it.